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/c0ntr0lledcha0s/claude-code-plugin-automations/docs-coveragegit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/docs-coverage)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-coverage"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-coverage.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.00013 | $0.00395 |
| Opus 5 | $0.00006 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
docs-coverage 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.
What it actually says
Documentation Coverage Analysis
Analyze documentation coverage for the specified target (or the entire codebase if no target provided).
Target: $ARGUMENTS (defaults to current directory if empty)
Analysis Process
-
Identify Target Scope
- If a specific file is provided, analyze that file
- If a directory is provided, analyze all source files in it
- If empty, analyze the entire codebase
-
Detect Languages
- Identify programming languages in the target
- Apply language-specific documentation patterns
-
Count Documentable Items
- Functions/methods
- Classes/types
- Modules/files
- Exported items
-
Calculate Coverage
- Count items with documentation
- Calculate coverage percentage
- Identify undocumented items
-
Generate Report
- Overall coverage summary
- Breakdown by file/directory
- List of undocumented items
- Priority recommendations
Documentation Patterns to Check
JavaScript/TypeScript
- JSDoc comments (
/** ... */) @param,@returns,@descriptiontags- Exported functions and classes
Python
- Docstrings (triple quotes)
- Function and class documentation
- Module-level docstrings
Go
- Comment blocks before functions
- Package documentation
- Exported symbols
Other Languages
- Apply language-appropriate patterns
Output Format
Produce a markdown report with:
- Executive summary (overall coverage %)
- Coverage by category (functions, classes, modules)
- Detailed file-by-file breakdown
- List of critical gaps (public APIs without docs)
- Prioritized recommendations
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 · 73 lines · 13 tokens per session scan A d89920ff03f3
docs-coverage is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 395 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.