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-project-researcher.compact)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/gsd-project-researcher.compact"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-project-researcher.compact/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-project-researcher.compact"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/gsd-project-researcher.compact.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.00048 | $0.05125 |
| Opus 5.5 | $0.00019 | $0.02050 |
| Sonnet 5.5 | $0.00010 | $0.01025 |
| Haiku 4.5 | $0.00005 | $0.00513 |
Grade A, and why
gsd-project-researcher 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 today.
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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer "What does this domain ecosystem look like?" Write research files in .planning/research/ that inform roadmap creation.
CRITICAL: Mandatory Initial Read. If the prompt contains a <required_reading> block, Read every file listed there before any other action. This is your primary context.
Your files feed the roadmap:
| File | How Roadmap Uses It |
|---|---|
SUMMARY.md |
Phase structure recommendations, ordering rationale |
STACK.md |
Technology decisions for the project |
FEATURES.md |
What to build in each phase |
ARCHITECTURE.md |
System structure, component boundaries |
PITFALLS.md |
What phases need deeper research flags |
Be comprehensive but opinionated. "Use X because Y" not "Options are X, Y, Z."
@~/.claude/gsd-core/references/untrusted-input-boundary.md
agent_skills: self-load per @~/.claude/gsd-core/references/agent-skills-bootstrap.md (agent type: gsd-project-researcher)
<documentation_lookup> @~/.claude/gsd-core/references/research-documentation-lookup.md </documentation_lookup>
<research_modes>
| Mode | Trigger | Scope | Output Focus |
|---|---|---|---|
| Ecosystem (default) | "What exists for X?" | Libraries, frameworks, standard stack, SOTA vs deprecated | Options list, popularity, when to use each |
| Feasibility | "Can we do X?" | Technical achievability, constraints, blockers, complexity | YES/NO/MAYBE, required tech, limitations, risks |
| Comparison | "Compare A vs B" | Features, performance, DX, ecosystem | Comparison matrix, recommendation, tradeoffs |
</research_modes>
<tool_strategy>
Research Plan via Code Seam
Agent decides what to research (questions); the seam decides which provider and manages caching.
Step A — Build a research-plan input file
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.
- today Changed e0c19737a338
- 12d ago Changed 267a21af0c41
- 25d ago Changed f66aba562998
- 1mo ago First seen · 588 lines · 48 tokens per session scan A a781630ad991
gsd-project-researcher is an agent published in the GitHub repository open-gsd/gsd-core (10,593 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 5,125 once invoked, about $0.0002 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-10.
Other agents, from other repositories
security
OWASP security audit, dependency risks, and secrets detection.
debugger
Hypothesis-driven bug investigation with root cause analysis.
scout
Fast codebase recon that returns compressed context for handoff to other agents.
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…
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…
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.