
agent-pulse
Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.
- Installs
- 47.5K
- Last 24h
- —
- Trending rank
- —
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jane-o-o-o-o/agent-pulse-skill --skill agent-pulse- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads agent-pulse automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
Agent Pulse
Purpose
Use the installed agent-pulse CLI as the source of truth for local AI-agent activity. The PyPI package is agentpulse-cli, while the command remains agent-pulse. Prefer running commands and summarizing their output over reading the Agent Pulse source code.
Always enable UTF-8 on Windows before running commands because Agent Pulse output contains emoji and box drawing:
$env:PYTHONUTF8='1'
$env:PYTHONIOENCODING='utf-8'
If agent-pulse is not on PATH, ask before installing dependencies. If the user approves, install the PyPI package or try running from a local project checkout:
pip install agentpulse-cli
python -m agent_pulse.cli --version
Source Keys
Use -P/--platform when the user asks about one agent tool instead of all local data:
hermes, claude, codex, deepseek, openclaw, copilot, aider, qwen,
opencode, goose, cursor, antigravity, amp
Choose Commands
Use this command selection table first:
| User wants | Run |
|---|---|
| Current status | agent-pulse status --json |
| Full dashboard | agent-pulse --json or agent-pulse --no-banner |
| Demo data | agent-pulse demo --json |
| Setup diagnosis | agent-pulse doctor --json |
| Recent sessions | agent-pulse --json --hours 24 --limit 20 |
| Top sessions | agent-pulse top --sort tokens --json |
| Top expensive sessions | agent-pulse top --sort cost --json --hours 168 |
| Model cost analysis | agent-pulse models --json |
| Model ranking | agent-pulse leaderboard --json --rank-by efficiency |
| Cost savings | agent-pulse optimize --json |
| Budget status | agent-pulse budget --json |
| Cost forecast | agent-pulse forecast --json |
| Cost anomaly check | agent-pulse anomaly --json |
| Health/CI check | agent-pulse health --json |
| Composite score | agent-pulse score --json |
| Search sessions | agent-pulse search "<query>" --json |
| Compare periods | agent-pulse compare --json |
| Compare projects | agent-pulse compare-projects --json |
| Activity calendar | agent-pulse heatmap --json |
| Smart recommendations | agent-pulse insights --json |
| Prometheus metrics | agent-pulse metrics --format prometheus |
| Export report | agent-pulse export -f markdown or agent-pulse export-html |
| Web dashboard | agent-pulse web --port 8765 |
| REST API | agent-pulse api --port 8766 |
| MCP tools | agent-pulse mcp --list-tools |
If the installed command lacks an option, run agent-pulse <command> --help and adapt.
Workflow
- Start with
agent-pulse doctor --jsononly when the user asks why data is missing, asks for setup help, or a normal data command returns no sessions. - Use JSON output whenever possible. Summarize the fields that matter: sessions, tokens, tools, search calls, model breakdown, source breakdown, estimated cost, warnings.
- Use time filters for scoped questions. Default to 24 hours for "recent" and 168 hours for "this week":
agent-pulse status --json --hours 24
agent-pulse --json --hours 168 --limit 50
- Use platform filters when the user asks about a specific agent system:
agent-pulse --json -P codex --hours 24
agent-pulse --json -P claude --hours 24
agent-pulse top --json -P aider --sort cost
agent-pulse status --json -P cursor
- For cost questions, pair summary, model, and top-session views:
agent-pulse status --json --hours 24
agent-pulse models --json --hours 24
agent-pulse top --sort cost --json --hours 24
agent-pulse optimize --json --hours 168
- For trend and risk questions, use forecast/history/compare/anomaly:
agent-pulse forecast --json
agent-pulse history --json
agent-pulse compare --json
agent-pulse anomaly --json
- For setup, use the discovery commands before guessing paths:
agent-pulse doctor --json
agent-pulse scan --json --details
agent-pulse config show
Interpreting Results
- Treat
total_cost_usdas an estimate based on Agent Pulse's local model pricing table. - Report both cost and token volume; low-cost models can still have very high token usage.
- Distinguish sources such as
codex,claude,hermes,deepseek,openclaw,aider,cursor,opencode, andgoose. - Mention if
doctorreports missing optional sources, missingdev_root, or optional web dependencies. - If no sessions appear, check
doctor, then try a wider time window such as--hours 168. - Check whether the user asked for a source (
-P) filter, a model filter, or a project comparison before giving overall totals. - If a command emits plain text instead of JSON or fails because an installed version is older, run
agent-pulse <command> --helpand use the closest supported option.
Reports
For a short human-readable answer, run JSON commands and summarize.
For artifacts, prefer:
agent-pulse report --period daily
agent-pulse export -f markdown
agent-pulse export-html
Do not invent exact savings or costs. Use the CLI output.
Integrations
Use the web and API extras only when the user asks for a browser dashboard or programmatic server. Ask before installing missing extras:
pip install "agentpulse-cli[web]"
agent-pulse web --port 8765
agent-pulse api --port 8766
For monitoring pipelines:
agent-pulse metrics --format prometheus
agent-pulse health --cost-limit 100 --token-limit 1000000 --json
MCP
Use MCP mode when the user wants other AI clients to query Agent Pulse:
agent-pulse mcp --list-tools
agent-pulse mcp
When explaining MCP, mention that it exposes tools such as status, forecast, top sessions, model analytics, optimization, health, search, and leaderboard.
Local Helper
This skill includes scripts/run_agent_pulse_snapshot.py, which runs a compact set of JSON-friendly Agent Pulse checks and prints a combined summary:
python scripts/run_agent_pulse_snapshot.py --hours 24 --days 7
FAQ
What does the agent-pulse skill do?
Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.
How do I install agent-pulse?
Run npx skills add https://github.com/jane-o-o-o-o/agent-pulse-skill --skill agent-pulse in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-pulse/ (personal) or .claude/skills/agent-pulse/ (project).
Which AI agents can use agent-pulse?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is agent-pulse safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains agent-pulse?
It is published by jane-o-o-o-o in jane-o-o-o-o/agent-pulse-skill. It has 47,534 recorded installs.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.