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.
git 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/commands/hoangsonww/claude-code-agent-monitor/runs)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/runs"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/runs/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/commands/hoangsonww/claude-code-agent-monitor/runs"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/runs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00014 | $0.00072 |
| Opus 5 | $0.00007 | $0.00036 |
| Sonnet 5 | $0.00003 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
runs 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 8d 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 ccam run list and ccam run history --limit 30. Summarize live handles
first, then recent persisted runs with provider, model, working directory,
status, session ID, and duration. Do not start or stop anything.
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.
- 8d ago First seen · 8 lines · 14 tokens per session scan A cd6e3aeb2a68
runs is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 72 once invoked, about $0.0001 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 commands, from other repositories
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
create-features
Create features from implementation plan.
work
Start working on a GitHub issue — fetch context, create branch, plan solution, and optionally open a PR.
create-task
Create a GitHub issue with project board integration.
OPSX: Archive
Archive a completed change in the experimental workflow.
tasks
Use the Skill tool to run agentii:tasks on this workspace (spec 046 kit skill — read its SKILL.md for the full methodology, gates and invocation).