Claude Code Agent Monitor is a dashboard that records and displays activity from Claude Code and Codex coding-agent sessions, including tool use and subagent coordination. It is for people who need live visibility into agent work through a web interface or native desktop app. The catalogue entries extend Claude Code with skills, commands, agents, plugins, instructions, hooks, and settings related to the monitor.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill run-agentgit clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-MonitorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/run-agent)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/run-agent"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/run-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/run-agent"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/run-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 38 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.00370 |
| Opus 5.5 | $0.00026 | $0.00148 |
| Sonnet 5.5 | $0.00013 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
run-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run Agent
Use ccam run against the local dashboard.
Workflow
- Verify the provider binary:
ccam run binary claudeccam run binary codex
- Discover supported models with
ccam run models <provider>. - Confirm the working directory with
ccam run cwds. - Show the exact launch settings before starting. Include provider, prompt, working directory, model, approval mode, sandbox, and resume session ID.
- Start only after user confirmation:
ccam run start --provider codex --cwd /path/to/repo \
--prompt "Review the current changes" \
--permission on-request --sandbox workspace-write --yes
- Inspect with
ccam run listorccam run get <id> --envelopes. - Send follow-ups with
ccam run send <id> --text "..." --provider codex --yes. - Stop with
ccam run stop <id> --yes.
Safety
- Never use
danger-full-accessunless the user explicitly requests it. - Do not start, message, or stop a run without confirmation.
- Preserve the provider used to start the run when sending messages.
- Treat run history as evidence. Do not claim completion from process status alone when the final output or persisted session shows an error.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 42 lines · 64 tokens per session scan A 70556aa39e65
run-agent is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (1,124 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 370 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
lead-orchestration
Use when you are the LEAD (main session) and an owner request arrives that needs agents -- intake, routing, briefs, follow-up, blocks, verification, learning, report. Canonical procedure from request to verified report; not for sub-agents executing a brief.
radin-record
Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session. Logs bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation.
radin-do
Use for /radin-do . Records one ad-hoc prompt as a backlog entry, then executes just that task.
radin-batch
Use for "work through my backlog", or name an epic or task to run only those. Works tasks via sub-agents in priority order, one commit each, and plans first the entries radin-record flagged as needing a plan.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.