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/sienklogic/plan-build-run/forensicsgit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/forensics)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/forensics"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/forensics.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.00020 | $0.00051 |
| Opus 5 | $0.00010 | $0.00026 |
| Sonnet 5 | $0.00004 | $0.00010 |
| Haiku 4.5 | $0.00002 | $0.00005 |
Grade A, and why
forensics 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 3d 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.
What it actually says
This command is provided by the pbr:forensics skill.
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.
- 3d ago First seen · 7 lines · 20 tokens per session scan A 650d5b999664
forensics is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 51 once invoked, about $0.0001 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 commands, from other repositories
doncheli-audit
OWASP Top 10 security audit — injection, XSS, secrets, access control.
doncheli-design-ui
Generate UI/UX designs from specs with Figma link or HTML preview and approval flow.
doncheli-estimate
Estimate effort using 4 models — Function Points, Planning Poker AI, COCOMO, Historical.
doncheli-plan
Generate technical blueprint with architecture and API contracts.
doncheli-prd
Generate PRD from Figma, briefs, user research — Product Requirement Document.
doncheli-review
Peer review in 7 dimensions — functionality, tests, performance, architecture, security, maintainability, docs.