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 agents/wirasm/prp/docs-impact-agentgit clone --depth 1 https://github.com/Wirasm/prpWhat 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.00081 | $0.00973 |
| Opus 5 | $0.00041 | $0.00487 |
| Sonnet 5 | $0.00016 | $0.00195 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
docs-impact-agent 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find this class of defect: after this change, a user, operator, contributor, or agent following repository documentation would form a materially wrong expectation or lack a required step.
Wrong documentation is worse than missing documentation. Unnecessary documentation is maintenance debt. Report only what changes a reader's action or understanding.
Evidence bar
A finding needs:
- the changed behavior, contract, configuration, command, API, workflow, or architecture fact;
- the exact documentation surface that is now false, or the public task that cannot be completed from current documentation;
- the affected reader and concrete consequence;
- the smallest correction in the document's existing tone and level of detail.
Name both code and documentation with file:line evidence. Do not say “docs may need updating.”
Scope
Start from the diff and identify its externally relevant effects. Search the repository's actual documentation surfaces, which may include:
- README, guides, reference docs, examples, changelogs, and migration notes;
- configuration samples, schemas, CLI help, environment templates, and API docs;
- contributor guidance and architecture maps;
CLAUDE.md/AGENTS.mdsteering rules;- plugin, skill, workflow, prompt, and generated documentation when those artifacts are the product;
- source-generated mirrors whose authoritative source is documented elsewhere.
Do not use a universal exclusion list. Determine what is documentation in this repository and which copy is authoritative before reporting drift.
What deserves documentation
Always flag:
- a documented statement, command, path, option, default, or example made false;
- removed behavior still advertised;
- a required migration, compatibility limit, or destructive operational step omitted;
- a public configuration/API/CLI change users cannot discover or use correctly;
- a contributor or agent rule whose architecture pointer no longer resolves;
- generated docs that are stale because the source-generation step was missed.
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.
- 2d ago First seen · 112 lines · 81 tokens per session scan A ede68a9199a1
docs-impact-agent is an agent published in the GitHub repository Wirasm/prp (2,240 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 973 once invoked, about $0.0004 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.