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/standup)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/standup"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/standup/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/standup"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/standup.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.00019 | $0.00334 |
| Opus 5 | $0.00010 | $0.00167 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
standup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s 'http://localhost:4820/api/sessions?limit=50'` What it actually says
Generate a fast daily standup from Agent Monitor data at http://localhost:4820.
Target day from $ARGUMENTS: "today" or empty = the last calendar day; "yesterday" = the day before. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.
- Fetch sessions:
curl -s 'http://localhost:4820/api/sessions?limit=50'Keep sessions whosestarted_atfalls on the target day. - Fetch cost:
curl -s http://localhost:4820/api/pricing/costfor thetotal_costand per-modelbreakdown.
Print a compact standup (aim for a 30-second read):
- One-line summary suitable for pasting into Slack (e.g. "5 sessions across 3 projects, 4 done, $0.7421").
- Done / In progress grouped by project (
cwd): per group list session count and statuses (completed,running,error,abandoned). - Errors / blockers: any session with
statuserrororabandoned; name the project. - Numbers: total sessions, completion rate (completed / total), and estimated cost in USD to 4 decimals.
Keep it terse — this is a one-shot, not a full report. Cite only numbers returned by the API.
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 · 23 lines · 19 tokens per session scan A 26389619e712
standup is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 334 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
sprint-plan
Plan a sprint with a calibrated, realistic commitment.
retro
Run a structured sprint retrospective from notes.
lessons-compact
Compact MEMORY/LESSON.md by deduplicating near-identical lessons, merging same-root-cause lessons, and pruning stale ones — without losing any unique signal. Delegates the analysis to the lessons-compactor agent.
prompt-history
Manage history of created and optimized prompts.
lessons
View project lessons in MEMORY/LESSON.md (project root) and append a compact "never reproduce" lesson.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.