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/reganomalley/claudiaWrote 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/reganomalley/claudia/health)<a href="https://agentmods.dev/commands/reganomalley/claudia/health"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/health/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/reganomalley/claudia/health"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/health.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.00016 | $0.00740 |
| Opus 5 | $0.00008 | $0.00370 |
| Sonnet 5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia Health Check
You are Claudia, running a project health audit. Scan the current project and report findings.
Focus area (optional): $ARGUMENTS
Audit Process
1. Discover the Stack
Read package.json (or pyproject.toml, go.mod, etc.) and scan for config files:
Glob: **/package.json, **/tsconfig.json, **/Dockerfile, **/docker-compose.yml,
**/.env.example, **/prisma/schema.prisma, **/.github/workflows/*.yml,
**/vite.config.*, **/next.config.*, **/vitest.config.*, **/jest.config.*,
**/.eslintrc.*, **/tailwind.config.*
2. Run Checks
Security:
- .env file is gitignored (check
.gitignore) - No hardcoded secrets in source (grep for
sk-,AKIA,password =) - Dependencies don't have known vulnerabilities (run
npm audit --jsonif Node.js) - HTTPS enforced in configs
- CORS configured (not
*in production) - Auth library used (not hand-rolled)
Testing:
- Test framework configured (jest.config, vitest.config, pytest.ini)
- Tests exist (glob for
**/*.test.*,**/*.spec.*,**/test_*.py) - CI runs tests (check
.github/workflows/) - Test coverage configured
Dependencies:
- Lock file exists and tracked (package-lock.json, yarn.lock, pnpm-lock.yaml)
- No deprecated packages (check against known list)
- Node/Python version pinned (engines in package.json, .python-version, .nvmrc)
- devDependencies not in production dependencies
Architecture:
- README exists
- Environment variables documented (.env.example)
- Dockerfile uses multi-stage builds (if containerized)
- TypeScript strict mode enabled (if using TS)
- Linting configured
Performance:
- Images optimized (next/image, responsive images)
- Bundle analysis available
- Caching configured (Redis, CDN, HTTP cache headers)
3. Report Format
Present findings as a health report:
## Project Health: [project-name]
**Stack:** [detected framework, DB, hosting]
**Overall:** [Good / Needs Attention / Critical Issues]
### Security [score/5]
- [finding]
- [finding]
### Testing [score/5]
- [finding]
### Dependencies [score/5]
- [finding]
### Architecture [score/5]
- [finding]
### Top 3 Actions
1. [most impactful fix]
2. [second most impactful]
3. [third]
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.
- 10d ago First seen · 94 lines · 16 tokens per session scan A dfe5162863d8
health is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 740 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-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.