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 skills add open-gsd/gsd-pi --skill gsd-blocker-recoverygit 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/gsd-blocker-recovery)<a href="https://agentmods.dev/skills/open-gsd/gsd-pi/gsd-blocker-recovery"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/gsd-blocker-recovery/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/open-gsd/gsd-pi/gsd-blocker-recovery"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/gsd-blocker-recovery.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.00114 | $0.01810 |
| Opus 5.5 | $0.00046 | $0.00724 |
| Sonnet 5.5 | $0.00023 | $0.00362 |
| Haiku 4.5 | $0.00011 | $0.00181 |
Grade A, and why
gsd-blocker-recovery 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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
| Concept | Meaning |
|---|---|
Blocker ID (workflow_blockers.blocker_id) |
Identifies one blocker. It is not a Recovery Action ID and not an Attempt ID. |
eligible: true |
Clear-only association eligibility from /gsd blocker inspect: the blocker is open, human-owned, and associated with exactly one open auto pause. It does NOT mean the problem is repaired and never means a Task succeeded. |
| Native blocker resolution | A human clears an eligible blocker and its pause via /gsd blocker resolve <id> resolved <reason> in the native terminal, with nonblank evidence and an explicit y approval. RPC/headless callers can only inspect. Clearing resumes nothing. |
| Task Recovery Action resume | One gated continuation for an agent-owned abort/remediation: it authorizes exactly one new (lineage-linked successor) Task Attempt after a real repair, via gsd_task_recovery_resume or the operator bridge /gsd recover <recoveryActionId>, with repair summary + concrete evidence. The authorization is consumed once. |
| Verified Task completion | The Attempt (failed or successor) settles and completes only through the normal host-verification path. Failure or interruption never equals completion. |
Human auto-pause blocker kinds (the only ones a human can clear): missing_authority, missing_access, external_dependency, consent, ambiguous_intent, subjective_uat, user_limit.
<core_principle>
BLOCKER APPROVAL IS HUMAN AND NATIVE-TERMINAL-ONLY. /gsd blocker resolve runs an interactive approval component in the real terminal; the caller must press y. In RPC/headless contexts that component never executes, so resolution is impossible there — inspect only. Never synthesize, simulate, or automate that approval; never impersonate the user or fabricate input markers; a dialog response or command exit is not consent. There is no agent or RPC path to approve a blocker resolution.
RESUME IS GATED, NOT FREE. A recovery resume is legitimate only when the recorded cause is genuinely repaired and concrete verification evidence accompanies it. The durable guards fail closed: recovery action exists; action is abort or remediate and agent-owned; not linked to a Blocker; not already resumed; Task lifecycle ready or in_progress; Attempt settled and still owning the causal route; no open blockers. The authorization is consumed by the next lineage-linked Task Attempt and cannot be reused.
FAIL-CLOSED FENCES ARE LOAD-BEARING. Resolution re-verifies the checkout, the existing writable database binding, and the inspected snapshot (revision + authority epoch) before the atomic clear. A mismatch refuses and requires a fresh inspect — that is stale-consent protection, not a bug to route around.
DIAGNOSIS STAYS READ-ONLY. In forensics or find_root_cause_only debug mode, stay inside that goal: inspect, analyze, and hand the operator the route. Do not clear, approve, resume, or repair state as a side effect.
</core_principle>
1. Diagnose read-only
- Inspect the blocker:
/gsd blocker inspect <blockerId>(or thegsd_*status/read tools). Read the returned snapshot:eligible,failure, blocker{id, kind, owner, scope, origin, lifecycleState}, pause,revision,authorityEpoch. - For a failed Task attempt, find the recoveryActionId in the auto-mode error/notification text (it is embedded in prose, e.g. "...recoveryActionId: ). Resume it with /gsd recover .").
- Post-mortem evidence lives under
.gsd/(activity, journal, metrics, pauses); theforensicsskill covers that read-only sweep.
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.
- today First seen · 94 lines · 114 tokens per session scan A f9da3aebcea5
gsd-blocker-recovery is a skill published in the GitHub repository open-gsd/gsd-pi (1,334 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 1,810 once invoked, about $0.0005 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-10-22.
Other skills, from other repositories
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-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-review-backlog
Review and promote backlog items to active milestone.
gsd-map-codebase
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents.