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 skills add SienkLogic/plan-build-run --skill 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/skills/sienklogic/plan-build-run/forensics)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/forensics"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/forensics/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/skills/sienklogic/plan-build-run/forensics"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/forensics.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.00023 | $0.01013 |
| Opus 5.5 | $0.00009 | $0.00405 |
| Sonnet 5.5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP — DO NOT READ THIS FILE. You are already reading it.
/pbr:forensics — Post-Mortem Investigation
Read-only investigation for failed or stuck workflows. Analyzes git history, .planning/ artifacts, and file system state to detect anomalies. Writes a diagnostic report. Does NOT modify project files.
Step 0 — Banner
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► FORENSICS ║
╚══════════════════════════════════════════════════════════════╝
Step 1 — Get Problem Description
If $ARGUMENTS is empty, ask: "What went wrong? Describe the issue — e.g., 'autonomous mode got stuck on phase 3', 'execute-phase failed silently', 'commits seem wrong'."
Step 2 — Gather Evidence
Collect data from all available sources. Missing sources are fine — adapt.
2a. Git History
git log --oneline -30
git log --format="%H %ai %s" -30
git log --name-only --format="" -20 | sort | uniq -c | sort -rn | head -20
git status --short
git diff --stat
Record: commit timeline, most-edited files, uncommitted changes.
2b. Planning State
Read if they exist: STATE.md, ROADMAP.md, config.json. Extract current phase, last session, blockers.
2c. Phase Artifacts
For each phase in .planning/phases/*/, check which artifacts exist vs expected (PLAN, SUMMARY, VERIFICATION, CONTEXT, RESEARCH).
2d. Worktree State
git worktree list
Check for orphaned worktrees from crashed agents.
Step 3 — Detect Anomalies
Stuck Loop Detection
Same file in 3+ consecutive commits within a short time window. HIGH confidence if commit messages are similar.
Missing Artifact Detection
Phase appears complete (has commits, past in roadmap) but lacks PLAN, SUMMARY, or VERIFICATION.
Abandoned Work Detection
Large gap between last commit and now, with STATE.md showing mid-execution.
Crash/Interruption Detection
Uncommitted changes + STATE.md active + orphaned worktrees.
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.
- 1mo ago First seen · 145 lines · 23 tokens per session scan A a74608133d04
forensics is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,013 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Generate a conventional commit message for staged changes.
git-advanced-workflows
Advanced Git workflows - rebase, cherry-pick, bisect, worktrees, reflog - for clean history and recovery.
git
Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.