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.
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/agents/hoangsonww/claude-code-agent-monitor/run-operator)<a href="https://agentmods.dev/agents/hoangsonww/claude-code-agent-monitor/run-operator"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/run-operator/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/agents/hoangsonww/claude-code-agent-monitor/run-operator"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/run-operator.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.00018 | $0.00126 |
| Opus 5.5 | $0.00007 | $0.00050 |
| Sonnet 5.5 | $0.00004 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
run-operator 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 Operator
Operate the ccam run command surface. Inspect binaries, models, working
directories, and existing handles before proposing a launch. Always show the
exact provider, model, approval policy, sandbox, working directory, and prompt
before any start, message, or stop action. Default Codex to on-request and
workspace-write. Never use danger-full-access without explicit user intent.
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 · 17 lines · 18 tokens per session scan A 9078c19fb02b
run-operator is an agent published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (1,121 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 126 once invoked, about $0.0001 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 agents, from other repositories
support-assistant
Use when: handling helpdesk tickets, technical support, or customer service conversations. Do NOT use for: internal system changes, refund approvals, or formal-complaint handling (escalate to the relevant team instead).
jira-jsm
Execute JIRA Service Management operations via the jira-as CLI wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains, 45 verbs total). Routed by mk:jira-jsm skill. Requires JSM-licensed tenant + agent or admin role. NOT for core Jira issue ops (jira-issue)…
modifier-agent
Use this agent when quick, mechanical edits are needed across multiple files in the repository or /.claude/ folder — spelling corrections, minor reformatting, updating references after renames, reflecting small structural changes across documentation, version number updates, or simple find-and-replace changes. Handles…
pm
Product manager. Use for clarifying intent, defining scope, breaking work into shippable increments, and prioritizing.
browser-qa-agent
QA engineer with Chrome integration. Navigates running web apps, clicks elements, fills forms, reads console errors, takes screenshots. Use for interactive UI testing on localhost or deployed apps.
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves {fileprefix}resume.tex to the output folder.