gsd-project-researcher

gsd-project-researcher is an agent for Claude Code from gsd-build/get-shit-done. It costs 48 tokens per session (4,473 once invoked), scanned A, original, MIT.

A project-research agent that investigates the ecosystem around a planned software project. It writes separate reports about technologies, features, architecture, and risks in a .planning/research/ folder.

In plain words
What is it for?
It is used before creating a project roadmap or starting a milestone. Its reports guide technology choices, feature scope, system structure, and areas needing more investigation.
Why use it?
It helps make roadmap decisions using researched information instead of starting with guesses about the domain or tools.

Agent for Claude Code

Written for Claude Code: PostToolUse hook event.

Good fit It is used before creating a project roadmap or starting a milestone. Its reports guide technology choices, feature scope, system structure, and areas needing more investigation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gsd-build/get-shit-done/gsd-project-researcher
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gsd-build/get-shit-done

Made for: Claude Code.

Wrote 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.

agentmods badge for gsd-project-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/gsd-build/get-shit-done/gsd-project-researcher/github.svg)](https://agentmods.dev/agents/gsd-build/get-shit-done/gsd-project-researcher)
Your own site
<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.

agentmods 80×15 button for gsd-project-researcher

Your own site · 80×15
<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>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,473 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash e6a2b86b87db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

agents/gsd-project-researcher.md · 678 lines

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:

  1. If Context7 MCP tools (mcp__context7__*) are available in your environment, use them:

    • Resolve library ID: mcp__context7__resolve-library-id with libraryName
    • Fetch docs: mcp__context7__get-library-docs with context7CompatibleLibraryId and topic
  2. 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:

  1. Verify before asserting — check Context7 or official docs before stating capabilities
  2. Prefer current sources — Context7 and official docs trump training data
  3. Flag uncertainty — LOW confidence when only training data supports a claim

Read the full file on GitHub · 678 lines

Changes

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.

  1. 11d ago First seen · 678 lines · 48 tokens per session scan A e6a2b86b87db

Subscribe to this mod's changes

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.