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 | $0.00032 | $0.00185 |
| Sonnet 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 9d 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.
- 9d 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 (991 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. 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.
radin-execute
Work through a project's whole backlog: prioritize every task, execute each via a sub-agent, commit after each. Use when the user wants the entire backlog processed ("work through my backlog"), not one named task. Delegates all implementation to sub-agents; clarifies ambiguity by asking the user rather than guessing.
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…
radin-show
Print the current project's backlog to the terminal. Use for /radin-show, "show me the backlog", "what's in the backlog", "list backlog items", "print the backlog".
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.
orchestrating-work
Principles for multi-agent workflow execution. Use when coordinating agents, accepting or rejecting agent work, executing producer-critic cycles, or running any multi-phase orchestrated task.