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 NickCrew/Claude-Cortex --skill doc-maintenancegit clone --depth 1 https://github.com/NickCrew/Claude-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/skills/nickcrew/claude-cortex/doc-maintenance)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/doc-maintenance"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/doc-maintenance.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.00094 | $0.02473 |
| Opus 5 | $0.00047 | $0.01236 |
| Sonnet 5 | $0.00019 | $0.00495 |
| Haiku 4.5 | $0.00009 | $0.00247 |
Grade A, and why
doc-maintenance 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 4d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Maintenance
Systematically audit, organize, and remediate project documentation by comparing the codebase against existing docs to find staleness, gaps, and misorganization.
When to Trigger
- After merging a feature branch or completing a refactor
- After dependency upgrades or API changes
- When onboarding surfaces confusion about project docs
- Periodic maintenance (monthly or per-release)
- When
scripts/doc_audit.pyis run manually and reports findings
Workflow Overview
Phase 1: Audit → Run deterministic scan + haiku search agents
Phase 2: Triage → Classify findings by severity and action type
Phase 3: Remediate → Dispatch specialized agents to fix/create docs
Phase 4: Quality → docs-architect reviews all changes
Phase 1: Audit
Step 1a — Run the deterministic scan
Execute the bundled audit script to get a baseline report:
python3 skills/doc-maintenance/scripts/doc_audit.py
The script produces a structured report covering:
- Broken internal links (markdown
[text](path)pointing to missing files) - Orphan docs (files not linked from any other doc or README)
- Missing required structure (expected folders/files absent from
docs/ormanual/) - Stale-relative-to-code (docs whose referenced subtree has churned significantly since the doc was last touched — measured via git log of code commits between the doc's last edit and now, not absolute doc age, which produces noise on stable architecture docs)
- Empty or stub files (< 3 lines of content)
Pass --json for machine-readable output. Pass --root PATH to override project root detection.
Step 1b — Dispatch search agents
After the deterministic scan, launch subagents to perform deeper analysis.
Model selection is task-calibrated: haiku for pattern enumeration, sonnet for
multi-file correlation and judgment. See references/agent-dispatch.md for
full prompt templates.
Agent 1 — Code-to-doc coverage scan (subagent_type: "Explore", model: "haiku"):
Search the codebase for public APIs, CLI commands, config schemas, and exported modules.
Cross-reference against existing docs (presence-check via grep). Report anything undocumented.
Haiku is sufficient because the inner loop is pattern enumeration plus a presence grep.
What ships with it
3 files 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.
- 4d ago First seen · 227 lines · 94 tokens per session scan A fb04e20770d8
doc-maintenance is a skill published in the GitHub repository NickCrew/Claude-Cortex (38 stars, last pushed 2mo ago), licensed MIT. It adds 94 tokens to every session and 2,473 once invoked, about $0.0005 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
cad-reviewer-contract
Internal role contract, preloaded into every cad-reviewer rung agent. Not a user command.
cad-plan-checker-contract
Internal role contract, preloaded into every cad-plan-checker rung agent. Not a user command.
skill-health-check
A health-check tool for project instructions and coding-agent skills. It checks whether skill files, configuration instructions, chat modes, and project rules exist, agree with one another, and are up to date.
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
spring-security-jwt
Use when an application issues and validates its own first-party JWT access and refresh tokens, including authentication filters, password encoding, RBAC, and method security. For JWTs issued by Keycloak, Auth0, Okta, Cognito, or another authorization server, use oauth2-resource-server.
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.