coverage

A documentation-coverage command that checks whether every MDX file in the docs folder is listed in the project index. MDX is Markdown that can include interactive components.

In plain words
What is it for?
Use it to inventory MDX files, compare them with contributing/INDEX.md, and report untracked files while excluding generated API documentation.
Why use it?
It finds documentation files that the project's tracking and reconciliation process would otherwise miss.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/dork-labs/dorkos/coverage
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00543
Opus 5 $0.00008 $0.00271
Sonnet 5 $0.00003 $0.00109
Haiku 4.5 $0.00002 $0.00054

Measured 2d ago against content hash 2b5d7ace62ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

.claude/commands/docs/coverage.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Coverage Check

Verify that every MDX file in docs/ is tracked in contributing/INDEX.md. Untracked files are invisible to the docs reconciliation system and will drift without warning.

Task

1. Inventory all MDX files

List every .mdx file under docs/:

find docs/ -name '*.mdx' | sort

2. Parse INDEX.md coverage

Read contributing/INDEX.md and extract all MDX file paths from the External Docs Coverage table (the | MDX File | column). Also extract from the External Docs Maintenance table to catch any that appear in tracking but not in the coverage map.

3. Compare and report

For each MDX file found on disk, check if it appears in the INDEX.md coverage table.

Skip these from the comparison (auto-generated, not hand-authored):

  • Files under docs/api/ (auto-generated from OpenAPI spec)

Report format:

## Documentation Coverage Report

### Summary

- Total MDX files on disk: N
- Tracked in INDEX.md: N
- Auto-generated (skipped): N
- **Untracked: N**

### Untracked Files (need adding to INDEX.md)

| File | Suggested Source Patterns |
| ----------------------- | ------------------------- | --------- |
| `docs/path/to/file.mdx` | `suggested                | patterns` |

### Coverage Map Entries for Missing Files

No action needed — INDEX.md already tracks all hand-authored docs.

4. Offer to fix

If untracked files are found, ask:

Would you like me to add the missing files to contributing/INDEX.md?
- Yes, add them now
- No, just report

If yes, add each missing file to both the External Docs Coverage table and the External Docs Maintenance table in INDEX.md. For source patterns, inspect the file content to determine which source code areas it documents.

5. Also check for stale entries

Check if any files listed in INDEX.md no longer exist on disk (deleted or renamed). Report those as well so they can be cleaned up.

When to Run

  • After creating or renaming docs files
  • Periodically as a health check
  • Before a release to ensure nothing drifted

Read the full file on GitHub · 78 lines

Changes

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.

  1. 2d ago First seen · 78 lines · 15 tokens per session scan A 2b5d7ace62ae

Subscribe to this mod's changes

coverage is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 543 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.