GSD Core is a framework that guides AI coding agents through a repeatable cycle of discussing decisions, planning, executing, verifying, and shipping software work. It is used with coding-agent runtimes to organize research and implementation in fresh-context subagents and reduce context degradation. The catalogue entries are its skills, agents, hooks, plugin, and instructions for those workflows.
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-core --skill gsd-shipgit clone --depth 1 https://github.com/open-gsd/gsd-coreWrote 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-core/gsd-ship)<a href="https://agentmods.dev/skills/open-gsd/gsd-core/gsd-ship"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-ship/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-core/gsd-ship"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00018 | $0.00440 |
| Opus 5.5 | $0.00007 | $0.00176 |
| Sonnet 5.5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
gsd-ship 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 6d 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
Invoke this Pi skill with /skill:gsd-ship.
Pi dispatch (fail closed). Pi has no built-in subagent API; GSD provides the gsd_dispatch tool. Where a workflow step dispatches a named gsd-* role, call gsd_dispatch with role (the installed role name) and task (the full task text). A workflow that still writes the step as an Agent(...) call means the same: its subagent_type is the role and its prompt is the task. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If gsd_dispatch reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.
Pi includes. Pi does not expand @path references in a skill. Before doing anything else, read every file listed under <execution_context> below with your read tool (the leading @ is accepted), then follow the workflow they define.
(the text typed after the skill name)
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
Closes the plan → execute → verify → ship loop.
<execution_context> @GSD_PI_ENGINE_ROOT/gsd-core/workflows/ship.md </execution_context>
Execute the ship workflow from @GSD_PI_ENGINE_ROOT/gsd-core/workflows/ship.md end-to-end.
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.
- 6d ago Changed b2861f8747b9
- 7d ago Changed · -2 lines a9a741ea60e3
- 27d ago Changed · +5 lines b98d1e2ebb3a
- 1mo ago First seen · 25 lines · 18 tokens per session scan A eb23c16b4893
gsd-ship is a skill published in the GitHub repository open-gsd/gsd-core (10,936 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 440 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
gh
Install and configure the GitHub CLI (gh) for AI agent environments where gh may not be pre-installed and git remotes use local proxies instead of github.com. Provides auto-install script with SHA256 verification and GITHUBTOKEN auth with anonymous fallback. Use when gh command not found, shutil.which("gh") returns…
gsd-headless
Orchestrate GSD (Git Ship Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute dev workflows, monitor progress, check status, or control execution (pause/stop/skip/steer). Triggers on "run gsd", "create milestone", "execute project", "check gsd status"…
write-milestone-brief
Synthesize the current conversation into a milestone brief (PRD). Saves it as the milestone CONTEXT (gsdsummarysave) by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has…
spike-wrap-up
Package findings from a completed spike into a durable project-local skill that auto-loads on future similar work. Reads the latest .gsd/workflows/spikes/ dir, interviews the user on what's reusable, then writes .agents/skills/ /SKILL.md. Use when asked to "wrap up the spike", "package this as a skill", "make this…
gsd-blocker-recovery
GSD blocker and failed-run recovery authority. Use when a GSD run is blocked or paused on an auto-pause blocker, a Task attempt failed, a recovery action exists, or anyone asks to "clear the blocker", "unblock the run", "resolve the pause", or "resume the failed task". Explains the two enforced routes: blocker…
verify-before-complete
Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always …