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/thelobbi/claude/doc-auditgit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/thelobbi/claude/doc-audit)<a href="https://agentmods.dev/commands/thelobbi/claude/doc-audit"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/doc-audit.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.00000 | $0.02526 |
| Opus 5 | $0.00000 | $0.01263 |
| Sonnet 5 | $0.00000 | $0.00505 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
doc-audit 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 — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Audit Command
Generate comprehensive reports on documentation coverage, quality, and sync status.
Command Metadata
```yaml command: doc-audit description: Audit documentation coverage and generate quality reports category: documentation priority: medium auto_trigger: session-end (summary only) ```
Usage
```bash
Full audit report
/doc-audit
Audit specific agent
/doc-audit --agent coder-001
Audit current session
/doc-audit --session current
Export to Obsidian
/doc-audit --export obsidian
Focus on specific aspects
/doc-audit --check coverage /doc-audit --check sync-status /doc-audit --check quality /doc-audit --check gaps ```
Report Sections
1. Documentation Coverage
``` 📊 DOCUMENTATION COVERAGE ═══════════════════════════════════════
Repository: Alpha-1.4 Total Files: 847 Documented Files: 356
Coverage: 42.0% ████████░░░░░░░░░░ (Target: 70%)
By Document Type: ├─ READMEs: 15/20 (75.0%) ████████████████░░░░ ├─ Architecture: 8/10 (80.0%) ██████████████████░░ ├─ API Docs: 12/25 (48.0%) ███████░░░░░░░░░░░░░ ├─ Guides: 45/60 (75.0%) ████████████████░░░░ ├─ ADRs: 23/30 (76.7%) ████████████████░░░░ └─ Quick Starts: 5/15 (33.3%) ██████░░░░░░░░░░░░░░
Missing Documentation: ⚠ No README in: lib/utils/ ⚠ No Architecture doc for: payments module ⚠ No API docs for: /api/webhooks ⚠ No setup guide ```
2. Sync Status
``` 🔄 OBSIDIAN SYNC STATUS ═══════════════════════════════════════
Total Documents: 356 Synced: 342 (96.1%) Unsynced: 14 (3.9%) Failed: 0
Unsynced Documents: ├─ docs/deployment/azure.md (pending) ├─ docs/api/webhooks.md (pending) ├─ research/agents/coordinator.md (pending) └─ ... (11 more)
Last Sync: 2025-01-29 14:32:15 Next Scheduled Sync: 2025-01-29 15:00:00
Sync Queue:
- Pending: 14
- Processing: 0
- Failed: 0 ```
3. Quality Metrics
``` ⭐ DOCUMENTATION QUALITY ═══════════════════════════════════════
Average Word Count: 847 words/doc Average Quality Score: 78/100
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 · 412 lines · 0 tokens per session scan A f3459c637d8a
doc-audit is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,526 tokens. 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.