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-research-synthesizer)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/gsd-research-synthesizer"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-research-synthesizer/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-research-synthesizer"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-research-synthesizer.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.00037 | $0.03122 |
| Opus 5 | $0.00018 | $0.01561 |
| Sonnet 5 | $0.00007 | $0.00624 |
| Haiku 4.5 | $0.00004 | $0.00312 |
Grade A, and why
gsd-research-synthesizer 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 10d 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.
This is a copy
84% identical to gsd-research-synthesizer — 31 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/gsd:new-projectorchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
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.
Core responsibilities:
- Read all 4 research files (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
- Synthesize findings into executive summary
- Derive roadmap implications from combined research
- Identify confidence levels and gaps
- Write SUMMARY.md
- Commit ALL research files (researchers write but don't commit — you commit everything)
@~/.claude/gsd-core/references/untrusted-input-boundary.md
agent_skills: self-load per @~/.claude/gsd-core/references/agent-skills-bootstrap.md
<downstream_consumer> Your SUMMARY.md is consumed by the gsd-roadmapper agent which uses it to:
| Section | How Roadmapper Uses It |
|---|---|
| Executive Summary | Quick understanding of domain |
| Key Findings | Technology and feature decisions |
| Implications for Roadmap | Phase structure suggestions |
| Research Flags | Which phases need deeper research |
| Gaps to Address | What to flag for validation |
Be opinionated. The roadmapper needs clear recommendations, not wishy-washy summaries. </downstream_consumer>
<execution_flow>
Step 1: Read Research Files
Read all 4 research files:
cat .planning/research/STACK.md
cat .planning/research/FEATURES.md
cat .planning/research/ARCHITECTURE.md
cat .planning/research/PITFALLS.md
# Planning config is loaded by the commit step below, after the launcher preamble
Parse each file to extract:
- STACK.md: Recommended technologies, versions, rationale
- FEATURES.md: Table stakes, differentiators, anti-features
- ARCHITECTURE.md: Patterns, component boundaries, data flow
- PITFALLS.md: Critical/moderate/minor pitfalls, phase warnings
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.
- 10d ago First seen · 265 lines · 37 tokens per session scan A b3df8d149729
gsd-research-synthesizer is an agent published in the GitHub repository open-gsd/gsd-core (9,278 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 3,122 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to gsd-research-synthesizer, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
security
OWASP security audit, dependency risks, and secrets detection.
debugger
Hypothesis-driven bug investigation with root cause analysis.
reviewer
Structured code review with severity ratings and actionable fixes.
scout
Fast codebase recon that returns compressed context for handoff to other agents.
javascript-pro
Modern JavaScript specialist for browser, Node.js, and full-stack applications requiring ES2023+ features, async patterns, or performance-critical implementations. Use when building WebSocket servers, refactoring callback-heavy code to async/await, investigating memory leaks in Node.js, scaffolding ES module libraries…
typescript-pro
TypeScript specialist for advanced type system patterns, complex generics, type-level programming, and end-to-end type safety across full-stack applications. Use when designing type-first APIs, creating branded types for domain modeling, building generic utilities, implementing discriminated unions for state machines…