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 agentmods add skills/open-gsd/gsd-core/gsd-graphifynpx skills add open-gsd/gsd-core --skill gsd-graphifygit 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-graphify)<a href="https://agentmods.dev/skills/open-gsd/gsd-core/gsd-graphify"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-core/gsd-graphify.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.00022 | $0.09605 |
| Opus 5 | $0.00011 | $0.04803 |
| Sonnet 5 | $0.00004 | $0.01921 |
| Haiku 4.5 | $0.00002 | $0.00961 |
Grade A, and why
gsd-graphify 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ferrox-graphify — 95% identical, 50 lines differ
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.
CJS-only (graphify): graphify subcommands are not registered on gsd-tools query. Use the gsd_run launcher shim (defined in each bash block below) or invoke the binary directly: node <runtime-home>/gsd-core/bin/gsd-tools.cjs graphify … where <runtime-home> is your runtime's config directory (e.g. ~/.claude, ~/.hermes, ~/.cursor). See docs/CLI-TOOLS.md for details. Other tooling may still use gsd-tools query where a handler exists.
Step 0 -- Banner
Before ANY tool calls, display this banner:
GSD > GRAPHIFY
Then proceed to Step 1.
Step 1 -- Config Gate
Check if graphify is enabled by reading .planning/config.json directly using the Read tool.
DO NOT use the gsd-tools config get-value command -- it hard-exits on missing keys.
- Read
.planning/config.jsonusing the Read tool - If the file does not exist: display the disabled message below and STOP
- Parse the JSON content. Check if
config.graphify && config.graphify.enabled === true - If
graphify.enabledis NOT explicitlytrue: display the disabled message below and STOP - If
graphify.enabledistrue: proceed to Step 2
Disabled message:
GSD > GRAPHIFY
Knowledge graph is disabled. To activate:
node <runtime-home>/gsd-core/bin/gsd-tools.cjs config-set graphify.enabled true
Then run /gsd-graphify build to create the initial graph.
Step 2 -- Parse Argument
Parse $ARGUMENTS to determine the operation mode:
| Argument | Action |
|---|---|
build |
Run inline build (Step 3) |
query <term> |
Run inline query (Step 2a) |
status |
Run inline status check (Step 2b) |
diff |
Run inline diff check (Step 2c) |
| No argument or unknown | Show usage message |
Usage message (shown when no argument or unrecognized argument):
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.
- yesterday First seen · 205 lines · 22 tokens per session scan A d54c2b44e805
gsd-graphify is a skill published in the GitHub repository open-gsd/gsd-core (9,086 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 9,605 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
code-optimizer
Deep code optimization audit using parallel specialist agents that hunt performance anti-patterns via pattern-based detection, avoiding anchoring bias. Covers DB queries, memory leaks, algorithmic complexity, concurrency, bundle size, dead code, I/O/network, rendering, caching, and build config. Use when asked to…
director:resume
Pick up where you left off after a break. Restores your context automatically.
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".
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"…
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".