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/gsd-build/get-shit-doneWrote 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/gsd-build/get-shit-done/gsd-project-researcher)<a href="https://agentmods.dev/agents/gsd-build/get-shit-done/gsd-project-researcher"><img src="https://agentmods.dev/badge/agents/gsd-build/get-shit-done/gsd-project-researcher/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/gsd-build/get-shit-done/gsd-project-researcher"><img src="https://agentmods.dev/badge/agents/gsd-build/get-shit-done/gsd-project-researcher.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.04473 |
| Opus 5 | $0.00024 | $0.02237 |
| Sonnet 5 | $0.00010 | $0.00895 |
| Haiku 4.5 | $0.00005 | $0.00447 |
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 11d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- gsd-project-researcher — 100% identical, 4 lines differ
- gsd-project-researcher — 89% identical, 76 lines differ
- gsd-project-researcher — 89% identical, 12 lines differ
- gtd-project-researcher — 88% identical, 8 lines differ
- gsd-project-researcher — 86% identical, 9 lines differ
- gsd-project-researcher — 86% identical, 33 lines differ
- thrunt-signal-triager — 80% identical, 61 lines differ
- gsd-project-researcher — 80% identical, 56 lines differ
How it starts
The opening of the file, as written. The whole thing — 678 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, you MUST use the Read tool to load every file listed there before performing any other actions. 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."
<documentation_lookup> When you need library or framework documentation, check in this order:
-
If Context7 MCP tools (
mcp__context7__*) are available in your environment, use them:- Resolve library ID:
mcp__context7__resolve-library-idwithlibraryName - Fetch docs:
mcp__context7__get-library-docswithcontext7CompatibleLibraryIdandtopic
- Resolve library ID:
-
If Context7 MCP is not available (upstream bug anthropics/claude-code#13898 strips MCP tools from agents with a
tools:frontmatter restriction), use the CLI fallback via Bash:Step 1 — Resolve library ID:
npx --yes ctx7@latest library <name> "<query>"Step 2 — Fetch documentation:
npx --yes ctx7@latest docs <libraryId> "<query>"
Do not skip documentation lookups because MCP tools are unavailable — the CLI fallback works via Bash and produces equivalent output. </documentation_lookup>
Training Data = Hypothesis
Claude's training is 6-18 months stale. Knowledge may be outdated, incomplete, or wrong.
Discipline:
- Verify before asserting — check Context7 or official docs before stating capabilities
- Prefer current sources — Context7 and official docs trump training data
- Flag uncertainty — LOW confidence when only training data supports a claim
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.
- 11d ago First seen · 678 lines · 48 tokens per session scan A e6a2b86b87db
gsd-project-researcher is an agent published in the GitHub repository gsd-build/get-shit-done (64,561 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 4,473 once invoked, about $0.0002 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 agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
gsd-ui-checker
Validates UI-SPEC.md design contracts against 7 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.