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.
git clone --depth 1 https://github.com/rosudrag/ai-praxisWrote 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/rosudrag/ai-praxis/update-docs)<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/update-docs"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/update-docs/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/rosudrag/ai-praxis/update-docs"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/update-docs.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.00561 |
| Opus 5.5 | $0.00000 | $0.00224 |
| Sonnet 5.5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
update-docs 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 2mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-docs - Documentation Sync
Scan documentation for drift from source-of-truth files and update stale sections.
Instructions
You are a documentation maintenance specialist. Find where docs have drifted from the actual codebase and fix them.
Step 1: Identify Sources of Truth
Scan the project for authoritative files:
package.json / pyproject.toml / Cargo.toml → version, scripts, dependencies
.env.example / .env.template → environment variables
Dockerfile / docker-compose.yml → build & run commands
openapi.yaml / swagger.json → API endpoints
{{config_files}} → project-specific configuration
Step 2: Scan Documentation
Find all documentation files:
find . -name "*.md" -not -path "*/node_modules/*" -not -path "*/.git/*"
For each doc file, identify references to:
- CLI commands and scripts
- Environment variables
- File paths and directory structure
- Version numbers and dependency names
- API endpoints and parameters
- Configuration values
Step 3: Detect Drift
Compare doc references against source-of-truth files. Flag:
- Commands that no longer exist or have changed syntax
- Env vars documented but missing from
.env.example(or vice versa) - Paths that reference moved or deleted files
- Versions that don't match package manifests
- API endpoints that differ from the spec
Step 4: Update Stale Sections
For each stale section:
- Replace outdated content with current values from source files
- Wrap auto-generated content in markers:
<!-- AUTO-GENERATED: source=package.json --> ... <!-- /AUTO-GENERATED --> - Preserve any
<!-- USER_SECTION_START -->/<!-- USER_SECTION_END -->blocks
Step 5: Report
## Documentation Sync Report
| Metric | Count |
|--------|-------|
| Source files scanned | X |
| Doc files scanned | X |
| Stale sections found | X |
| Updates applied | X |
| Sections needing manual review | X |
### Changes Made
- **[file]** — [what changed and why]
### Manual Review Needed
- **[file:section]** — [why automation couldn't resolve this]
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.
- 2mo ago First seen · 83 lines · 0 tokens per session scan A 81a0d4191b24
update-docs is a command published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 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.
update-docs compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| update-docsrosudrag/ai-praxis | Command | 2 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |