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-plan-review-convergencegit 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-plan-review-convergence)<a href="https://agentmods.dev/skills/open-gsd/gsd-core/gsd-plan-review-convergence"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-plan-review-convergence/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-plan-review-convergence"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-plan-review-convergence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.01143 |
| Opus 5.5 | $0.00008 | $0.00457 |
| Sonnet 5.5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
gsd-plan-review-convergence 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoke this Pi skill with /skill:gsd-plan-review-convergence.
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.
Flow: Skill("gsd-plan-phase") → Agent→Skill("gsd-review") → check unresolved HIGH + actionable non-HIGH → Skill("gsd-plan-phase --reviews") → Agent→Skill("gsd-review") → ... → Converge or escalate
Replaces gsd-plan-phase's internal gsd-plan-checker with external AI reviewers (codex, claude, etc.). Plan-phase runs inline (bare Skill at depth 0) so it can spawn gsd-planner/gsd-plan-checker at depth 1. Review runs inside an isolated Agent (gsd-review is a Bash leaf — no sub-agents needed). Orchestrator only does loop control.
Orchestrator role: Parse arguments, validate phase, run plan-phase inline (Skill at depth 0), spawn an Agent for gsd-review, check unresolved HIGH and actionable non-HIGH counts, stall detection, escalation gate.
<execution_context> @GSD_PI_ENGINE_ROOT/gsd-core/workflows/plan-review-convergence.md @GSD_PI_ENGINE_ROOT/gsd-core/references/revision-loop.md @GSD_PI_ENGINE_ROOT/gsd-core/references/gates.md @GSD_PI_ENGINE_ROOT/gsd-core/references/agent-contracts.md </execution_context>
Flags:
--codex— Use Codex CLI as reviewer (default if no reviewer flag given ANDreview.default_reviewersis unset; otherwisereview.default_reviewerswins per ADR-0011 — #2315)--agy/--antigravity— Use Antigravity CLI as reviewer--claude— Use Claude CLI as reviewer (separate session)--coderabbit— Use CodeRabbit as reviewer (reviews the working-tree diff, not the source tree)--opencode— Use OpenCode as reviewer--qwen— Use Qwen Code CLI as reviewer (Alibaba Qwen models)--cursor— Use Cursor agent as reviewer--ollama— Use local Ollama server as reviewer (OpenAI-compatible, default hosthttp://localhost:11434; configure model viareview.models.ollama)--lm-studio— Use local LM Studio server as reviewer (OpenAI-compatible, default hosthttp://localhost:1234; configure model viareview.models.lm_studio)--llama-cpp— Use local llama.cpp server as reviewer (OpenAI-compatible, default hosthttp://localhost:8080; configure model viareview.models.llama_cpp)--kimi-code— Use Kimi Code CLI as reviewer (Moonshot AI)--all— Use all available CLIs and running local model servers--max-cycles N— Maximum replan→review cycles (default: 3)
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.
- 8d ago Changed 983d19fc6d6b
- 9d ago Changed · -6 lines cadd70a2e3db
- 29d ago Changed · +4 lines 7a1bbe5d9ba5
- 1mo ago Changed · +1 lines d5bbdf05531c
- 1mo ago Changed · -1 lines f2ef6fb90e2b
- 1mo ago First seen · 66 lines · 21 tokens per session scan A 7797fb9efc7b
gsd-plan-review-convergence is a skill published in the GitHub repository open-gsd/gsd-core (11,013 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,143 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
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
gsd-orchestrator
Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous…
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"…
api-design
Design or review an HTTP/REST/GraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to "design an API", "shape the endpoints", "design the schema", "add a new endpoint", "review this API", or when building/modifying a public…
create-mcp-server
Build, iterate, and evaluate Model Context Protocol (MCP) servers that expose external services as tools an LLM can call. Covers schema/tool design, error handling, pagination, MCP Inspector testing, and an eval set. Use when asked to "build an MCP server", "create an MCP tool", "wrap this API as MCP", "expose X to…