GSD Pi is a command-line coding agent and project workflow system that plans, implements, verifies, and tracks software work through milestones, tasks, Git worktrees, and stored project notes. It is for developers who want structured, longer-running agent sessions using different model providers. The catalogue entries extend GSD Pi with skills and agents.
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 skills/open-gsd/gsd-pi/forensicsnpx skills add open-gsd/gsd-pi --skill forensicsgit clone --depth 1 https://github.com/open-gsd/gsd-piWrote 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/open-gsd/gsd-pi/forensics)<a href="https://agentmods.dev/skills/open-gsd/gsd-pi/forensics"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/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.00112 | $0.02047 |
| Opus 5 | $0.00056 | $0.01024 |
| Sonnet 5 | $0.00022 | $0.00409 |
| Haiku 4.5 | $0.00011 | $0.00205 |
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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
activity/{seq}-{unitType}-{unitId}.jsonl— full tool-call and message stream per unitjournal/YYYY-MM-DD.jsonl— iteration-level events. Orchestrator path emitsorchestrator-*events (orchestrator-dispatch-match,orchestrator-guard-block,orchestrator-terminal, etc.); legacy loop events (dispatch-match,stuck-detected,guard-block,unit-start/end,terminal) can still appear on non-orchestrator paths.metrics.json— token/cost ledger; duplicatetype/identries indicate a stuck loopauto.lock— JSON snapshot of the currently-owning PID; stale lock = crash mid-unitforensics/— saved prior reportsdebug/— debug logs if enabledruntime/paused-session.json— serialized session when auto-mode pauseddoctor-history.jsonl— doctor check history
The /gsd forensics command pre-computes a forensic report with anomalies flagged. This skill is the manual investigation that goes deeper, or runs when the automated report isn't enough.
Invocation points:
/gsd forensicshas been run and user wants deeper analysis- Auto-mode exited unexpectedly, no obvious cause
- Same unit dispatched multiple times (stuck loop suspected)
- A session crashed and
auto.lockis stale - User reports "it just stopped" or "it did the wrong thing"
<core_principle>
READ-ONLY. Forensics touches no live state. Non-mutating inspection commands (e.g., ps, top -b, cat /proc/*) are allowed for checking process status or reading system files. Strictly prohibited: gsd_* writes, commands that modify state, executing binaries that produce side effects, writing to files (outside the final report), or re-running the failed unit. The evidence must stay pristine for future investigations.
SYMPTOM → ROOT CAUSE, WITH CITATIONS. Every claim in the report is backed by an artifact path and either a line number or a JSONL field. "The loop got stuck because of a race" is not useful; ".gsd/journal/2026-04-19.jsonl:142 shows stuck-detected with flowId X, caused by dispatch-guard.ts:87 returning the same unit after unit-end" is.
PRE-PARSED LEADS, NOT CONCLUSIONS. If /gsd forensics has surfaced anomalies, treat them as hypotheses to verify, not answers.
</core_principle>
Step 1: Locate the evidence
Read what's in .gsd/:
auto.lock— is it stale? Check PID againstps(read-only inspection, allowed). Stale = crash.- Most recent
.gsd/activity/*.jsonl— sort by mtime, newest first. That's the last unit that ran. - Today's
.gsd/journal/YYYY-MM-DD.jsonl— the iteration-level view. .gsd/metrics.json— does anytype/idappear more than once? (stuck loop signal).gsd/runtime/paused-session.json— if present, what was the pause reason?
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.
- 5d ago First seen · 154 lines · 112 tokens per session scan A db5b11b0a11b
forensics is a skill published in the GitHub repository open-gsd/gsd-pi (1,198 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 2,047 once invoked, about $0.0006 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 skills, from other repositories
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-import
Ingest external plans with conflict detection against project decisions before writing anything.
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
gsd-mempalace-recall
Recall decisions, patterns, and surprises from MemPalace before planning.