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/comment-analyzergit 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.00083 | $0.00971 |
| Opus 5 | $0.00042 | $0.00485 |
| Sonnet 5 | $0.00017 | $0.00194 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
comment-analyzer 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: changed prose tells a future reader something materially different from what the code, contract, or supported operation actually does.
Comments are not valuable by volume. Keep durable “why,” non-obvious invariants, boundary contracts, and operational constraints. Code should carry obvious “what.”
Evidence bar
Report only when all apply:
- Identify the exact changed comment, docstring, TODO, example, or operational note.
- Cite code, tests, schemas, configuration, or direct consumers that contradict it or show the promised constraint is incomplete.
- Name the concrete maintenance consequence: a caller uses the wrong contract, an invariant drifts, an operator follows unsafe guidance, or completed work remains marked pending.
- Give the smallest correction: fix, narrow, remove, or replace the prose with an enforceable reference.
A comment that is merely verbose, terse, or stylistically imperfect is not a finding.
Scope
Review comments and docstrings added or modified in the requested diff. Include TODO/FIXME/HACK markers, embedded examples, and comments a changed line makes newly false. Inspect the documented symbol and direct consumers, at most two hops from the prose.
Check:
- parameter, return, error, side-effect, and state-transition claims;
- “must,” “always,” “never,” ordering, units, ownership, and synchronization claims;
- examples against the actual API and current configuration;
- TODOs against implemented behavior and linked work;
- comments naming files, symbols, commands, versions, or supported variants;
- rationale that no longer matches the implementation choice.
Prefer executable enforcement for an invariant when the comment is compensating for a reachable violation, but leave the underlying type/seam finding to its specialist. Here, report the prose defect.
Missing-comment bar
Report a missing comment only when the change introduces durable knowledge that cannot be expressed clearly in code or types, such as:
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 · 83 tokens per session scan A 3868b4a3b4f8
comment-analyzer is an agent published in the GitHub repository Wirasm/prp (2,240 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 971 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.