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 agentmods add commands/alphaaiservice/cortex/health-checkgit clone --depth 1 https://github.com/alphaaiservice/cortexWrote 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/alphaaiservice/cortex/health-check)<a href="https://agentmods.dev/commands/alphaaiservice/cortex/health-check"><img src="https://agentmods.dev/badge/commands/alphaaiservice/cortex/health-check.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 | $0.00021 | $0.02026 |
| Opus 5 | $0.00010 | $0.01013 |
| Sonnet 5 | $0.00004 | $0.00405 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
health-check 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 3d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Health Audit
Run a full health check on this project.
Audit Categories
Use Agent tool (mode = "bypassPermissions") to run these audits in parallel:
1. Dependency Health
# Check for outdated packages
npm outdated 2>&1 || pip list --outdated 2>&1 || go list -u -m all 2>&1
# Check for vulnerabilities
npm audit 2>&1 || safety check 2>&1 || pip audit 2>&1
# Check for unused dependencies
npx depcheck 2>&1 || true
2. Code Quality Metrics
- Count total lines of code by language
- Identify largest files (potential refactoring targets)
- Find duplicated code patterns
- Check for TODO/FIXME/HACK comments
- Identify dead code or unused exports
3. Test Health
# Run tests with coverage
npm test -- --coverage 2>&1 || pytest --cov --cov-report=term-missing 2>&1
- Overall coverage percentage
- Files with 0% coverage
- Test-to-code ratio
4. Documentation Coverage
- README.md exists and is comprehensive?
- CONTRIBUTING.md exists?
- API documentation exists?
- Inline code documentation quality
- CHANGELOG maintained?
5. CI/CD Status
- CI pipeline configured?
- All pipeline stages present (lint, test, build, deploy)?
- Branch protection rules?
- Automated deployment?
6. Security Posture
- Secrets in code? (scan for API keys, passwords)
- .env files in .gitignore?
- HTTPS enforced?
- Dependency vulnerabilities
- OWASP Top 10 basic checks
7. Git Health
echo "=== Branch Count ==="
git branch -a | wc -l
echo "=== Stale Branches (>30 days) ==="
git for-each-ref --sort=-committerdate --format='%(committerdate:short) %(refname:short)' refs/heads/ | tail -10
echo "=== Commit Frequency (last 30 days) ==="
git log --oneline --since="30 days ago" | wc -l
echo "=== Large Files ==="
git rev-list --objects --all | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' | awk '/^blob/ {print $3, $4}' | sort -rn | head -10
Health Report
Generate PROJECT_HEALTH.md:
# Project Health Report
**Generated**: [date]
**Overall Score**: [A/B/C/D/F]
## Summary Dashboard
| Category | Score | Status |
|----------------|-------|--------|
| Dependencies | 8/10 | 🟢 |
| Code Quality | 7/10 | 🟡 |
| Test Coverage | 6/10 | 🟡 |
| Documentation | 5/10 | 🔴 |
| CI/CD | 9/10 | 🟢 |
| Security | 7/10 | 🟡 |
| Git Health | 8/10 | 🟢 |
## Priority Actions (Top 5)
1. [Most critical action item]
2. [Second priority]
3. ...
## Detailed Findings
[Per-category detailed results]
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.
- 3d ago First seen · 241 lines · 21 tokens per session scan A 1677248a64ab
health-check is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 28d ago), licensed MIT. It adds 21 tokens to every session and 2,026 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
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
alfred
Asistente contextual de Alfred Dev. Enruta automáticamente al flujo o comando operativo correcto.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
audit
Auditoría completa del proyecto con 4 agentes en paralelo.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.