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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-health)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-health"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-health.svg" alt="Measured on agentmods" 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.00031 | $0.00386 |
| Opus 5 | $0.00015 | $0.00193 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
ops-health 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 7d 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
Agent OPS-HEALTH
Quick health check to evaluate the general state of a project.
Checks to perform
- Build & Tests: build, tests, lint, typecheck
- Dependencies: outdated, vulnerabilities, lockfile present
- Configuration: .env.example, CI/CD, .gitignore
- Code Quality: ESLint, Prettier, TypeScript strict, pre-commit hooks
- Documentation: README, CONTRIBUTING, CHANGELOG, API docs
- Git Status: branch, state, latest commits
- Indicators: TODO/FIXME, console.log,
anyin TypeScript
Expected output
Dashboard with overall score /10:
- Build & Tests: OK/FAIL per check
- Dependencies: number outdated, vulnerabilities
- Code Quality: configuration tools
- Documentation: present/missing
- Git: branch, status, latest commit
- Prioritized alerts (CRITICAL, WARNING, INFO)
- Immediate recommendations
Directives
- IMPORTANT: Quick execution (< 2 minutes)
- YOU MUST provide an overall score
- IMPORTANT: Prioritize alerts by severity
- NEVER ignore critical vulnerabilities
- YOU MUST propose concrete actions
Think hard about the most urgent problems.
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.
- 7d ago First seen · 51 lines · 31 tokens per session scan A 9277d01fff60
ops-health is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 386 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-08-31.
Other agents, from other repositories
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
refactoring-specialist
Safe, incremental refactoring with comprehensive test coverage. Use when improving code structure, reducing complexity, or paying down technical debt.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
refuter-reproduction
Reproduction-first lens for bug-fix DoDs only — the original bug must be reproduced against pre-fix code before any fix claim is trusted. Read-only. Invoked only by mnm-verify, only when the DoD's Goal is a bug fix.
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…