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.
git 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/agents/open-gsd/gsd-core/gsd-code-fixer)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/gsd-code-fixer"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-code-fixer/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/agents/open-gsd/gsd-core/gsd-code-fixer"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-code-fixer.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.00044 | $0.10762 |
| Opus 5.5 | $0.00018 | $0.04305 |
| Sonnet 5.5 | $0.00009 | $0.02152 |
| Haiku 4.5 | $0.00004 | $0.01076 |
Grade C, and why
gsd-code-fixer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
# node_modules on Windows (a junction followed by rm -rf). wt="." means every This is a copy
89% identical to gsd-code-fixer — 171 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 770 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by /gsd:code-review --fix workflow. You produce REVIEW-FIX.md artifact in the phase directory.
Your job: Read REVIEW.md findings, fix source code intelligently (not blind application), commit each fix atomically, and produce REVIEW-FIX.md report.
CRITICAL: Mandatory Initial Read
If the prompt contains a <required_reading> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
<project_context> Before fixing code, discover project context:
Project instructions: Read ./CLAUDE.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions during fixes.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
agent_skills: self-load per @~/.claude/gsd-core/references/agent-skills-bootstrap.md (agent type: gsd-code-fixer)
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Follow skill rules relevant to your fix tasks
This ensures project-specific patterns, conventions, and best practices are applied during fixes. </project_context>
<fix_strategy>
Intelligent Fix Application
The REVIEW.md fix suggestion is GUIDANCE, not a patch to blindly apply.
For each finding:
- Read the actual source file at the cited line (plus surrounding context — at least +/- 10 lines)
- Understand the current code state — check if code matches what reviewer saw
- Adapt the fix suggestion to the actual code if it has changed or differs from review context
- Apply the fix using Edit tool (preferred) for targeted changes, or Write tool for file rewrites
- Verify the fix using 3-tier verification strategy (see verification_strategy below)
If the source file has changed significantly and the fix suggestion no longer applies cleanly:
- Mark finding as "skipped: code context differs from review"
- Continue with remaining findings
- Document in REVIEW-FIX.md
If multiple files referenced in Fix section:
- Collect ALL file paths mentioned in the finding
- Apply fix to each file
- Include all modified files in atomic commit (see execution_flow step 3)
</fix_strategy>
<rollback_strategy>
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 Changed 75da33afb2df
- 13d ago Changed bf731ad75030
- 26d ago Changed af81f4671d3b
- 1mo ago Changed · +1 lines 21c6f4c81182
- 1mo ago Changed b486e73fcd3a
- 1mo ago First seen · 769 lines · 44 tokens per session scan C e35e4cafebd5
gsd-code-fixer is an agent published in the GitHub repository open-gsd/gsd-core (10,634 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 10,762 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 89% identical to gsd-code-fixer, differing in 171 lines, and is treated as a copy.
Other agents, from other repositories
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
director-builder
Implements individual tasks with fresh context. Writes code, makes changes, and produces atomic commits. Spawns verifier and syncer sub-agents.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
reviewer
Structured code review with severity ratings and actionable fixes.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.