Borrowing it
Nothing to install: this file belongs to rcconsult/ppxai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rcconsult/ppxai/master/.claude/commands/docs-consolidate.mdgit clone --depth 1 https://github.com/rcconsult/ppxaiWrote 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/rcconsult/ppxai/docs-consolidate)<a href="https://agentmods.dev/commands/rcconsult/ppxai/docs-consolidate"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/docs-consolidate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rcconsult/ppxai/docs-consolidate"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/docs-consolidate.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01553 |
| Opus 5.5 | $0.00000 | $0.00621 |
| Sonnet 5.5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
docs-consolidate 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 10d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Consolidation
Review, consolidate, and clean up project documentation. Archives stale docs, fixes broken cross-references, and updates files to reflect current repo state.
Arguments
$ARGUMENTS- Optional scope:all(full review),archive(archive stale docs only),links(fix broken links only),top-level(review root .md files only). Default:all
Usage
Full documentation review and consolidation:
/docs-consolidate
/docs-consolidate all
Archive completed/stale docs only:
/docs-consolidate archive
Fix broken cross-references only:
/docs-consolidate links
Review and update top-level .md files only:
/docs-consolidate top-level
Workflow
Phase 1: Inventory (all scopes)
-
List all documentation files:
ls *.md ls docs/*.md ls docs/archive/ -
Check git branch and version context:
git branch --show-current git log --oneline -5 -
Read key state files to understand current version and goals:
ROADMAP.md— current release statusCHANGELOG.md— what's been releaseddocs/TODO-v*.md— active work items (if any)
Phase 2: Archive Stale Docs (scopes: all, archive)
Criteria for archiving:
- TODO files for completed/released versions (e.g.,
TODO-v1.15.3.mdafter v1.15.3 is released) - Debug session logs that have been consolidated into summary docs
- Design/planning docs whose proposals have been fully implemented
- Release plans for completed releases
- Implementation quick-refs superseded by consolidated TODO docs
Archive procedure:
- Move with
git mv <file> docs/archive/ - Use descriptive names if needed (e.g.,
TODO-v1.16.0-file-navigation.mdinstead of generic name) - For files with many inbound references, consider replacing with a redirect stub instead of moving
- Check for and update all cross-references (see Phase 3)
Do NOT archive:
- Active TODO/planning docs
- User-facing guides (AGENT_MODE_GUIDE, CHECKPOINT_GUIDE, etc.)
- Architecture docs still relevant to current codebase
- Release notes (keep in
docs/, archive only very old ones if needed)
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.
- 10d ago Changed d41d96a52240
- 1mo ago First seen · 178 lines · 0 tokens per session scan A 9242113c4352
docs-consolidate is a command published in the GitHub repository rcconsult/ppxai (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,553 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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.