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 reliability-reportgit 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/reliability-report)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/reliability-report"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/reliability-report/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/reliability-report"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/reliability-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00190 |
| Opus 5 | $0.00023 | $0.00095 |
| Sonnet 5 | $0.00009 | $0.00038 |
| Haiku 4.5 | $0.00005 | $0.00019 |
Grade A, and why
reliability-report 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
Reliability Report
- Confirm the review window and data scope.
- Read stats, analytics, recent events, alert history, and workflow error propagation.
- Separate:
- Active, waiting, completed, error, and abandoned sessions
- API errors, tool failures, interrupted turns, and stale data
- Trigger, impact, recovery, and remaining risk
- Compare
PreToolUseandPostToolUsecounts without assuming every gap is a failure. Check matching event context. - End with ranked corrective actions and the exact evidence needed for any unresolved hypothesis.
- Remain read-only.
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.
- 8d ago First seen · 23 lines · 46 tokens per session scan A 93f578f8a3f2
reliability-report is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 190 once invoked, about $0.0002 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
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
breaking-changes
Use when checking whether a Claude Code update breaks our plugin ecosystem — hooks, agent frontmatter, manifest schema, or skill format.
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
systematic-debugging
Guides root cause investigation before proposing fixes. Use when debugging, diagnosing failures, investigating test errors, or tracing unexpected behaviour.
qa-check
Auto-detects the project's tech stack, then audits for Accessibility, Performance, and Code Quality. Works across WordPress/PHP, Python, Node/JS, and static web projects.