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 create-mcp-servergit 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/create-mcp-server)<a href="https://agentmods.dev/skills/open-gsd/gsd-pi/create-mcp-server"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/create-mcp-server.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.1 | $0.00090 | $0.01658 |
| Opus 5 | $0.00045 | $0.00829 |
| Sonnet 5 | $0.00018 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
create-mcp-server 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invocation points:
- User describes a service or API they want an LLM to reach
/gsd mcp initscaffolds config but there's a tool integration to build- Replacing a hand-rolled extension with a standard MCP server
<core_principle> THE QUALITY METRIC IS TASK COMPLETION, NOT SCHEMA VALIDITY. A server that lists 30 tools with cryptic names and empty descriptions passes the protocol but fails the point. The tool description is the only thing an LLM has to decide whether to call it — write it like documentation for a stranger under time pressure.
DESIGN FOR THE MODEL, NOT THE API. A raw REST endpoint is rarely the right tool. Group, filter, and pre-shape responses so the model gets what it needs to reason, not a 40KB JSON blob it has to summarize. Fewer, deeper tools beat many, shallow ones. </core_principle>
Step 1: Research and scope
- Study modern MCP design. Read the latest MCP protocol docs (not training data — fetch them). Read 2–3 reference implementations to see current patterns.
- Pick a framework. TypeScript is the default — the reference SDK is the most mature. Python is fine for data-heavy or ML adjacencies.
- Analyze the target API. Map the external service's endpoints, auth, rate limits, pagination, error shapes. Identify what a human workflow on top of it actually looks like — that's the cut line for tool design.
- Produce a brief. One page: what the server does, who calls it, the 5–10 tools you plan to expose, and the top 3 design trade-offs. Confirm with the user.
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.
- 7d ago First seen · 122 lines · 90 tokens per session scan A cc29de5c9c8e
create-mcp-server is a skill published in the GitHub repository open-gsd/gsd-pi (1,201 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,658 once invoked, about $0.0005 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.