gsd-phase-researcher

gsd-phase-researcher is an agent for Claude Code from KhanXBT/get-shit-done-antigravity. It costs 41 tokens per session (3,545 once invoked), scanned A, a copy of gsd-phase-researcher, MIT.

A research agent that investigates the technical details of a planned software project phase before someone breaks it into implementation tasks.

In plain words
What is it for?
Use it to research a phase, record findings in RESEARCH.md, follow decisions already made in CONTEXT.md, and provide information to the planning agent.
Why use it?
It identifies common tools, design patterns, risks, and confidence levels so the later plan is based on the project's technical context rather than assumptions.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/arshad/.claude/get-shit-done/bin/gsd-tools.cjs.

Good fit Use it to research a phase, record findings in RESEARCH.md, follow decisions already made in CONTEXT.md, and provide information to the planning agent.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

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-phase-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-phase-researcher/github.svg)](https://agentmods.dev/agents/khanxbt/get-shit-done-antigravity/gsd-phase-researcher)
Your own site
<a href="https://agentmods.dev/agents/khanxbt/get-shit-done-antigravity/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-phase-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-phase-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/khanxbt/get-shit-done-antigravity/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-phase-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,545 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 80% copy Near-identical to another mod 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.00041 $0.03545
Opus 5 $0.00020 $0.01773
Sonnet 5 $0.00008 $0.00709
Haiku 4.5 $0.00004 $0.00354

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

Security

Grade A, and why

gsd-phase-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 12d 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

This is a copy

80% identical to gsd-phase-researcher — 481 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.

agents/gsd-phase-researcher.md · 485 lines

How it starts

The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spawned by /gsd:plan-phase (integrated) or /gsd:research-phase (standalone).

Core responsibilities:

  • Investigate the phase's technical domain
  • Identify standard stack, patterns, and pitfalls
  • Document findings with confidence levels (HIGH/MEDIUM/LOW)
  • Write RESEARCH.md with sections the planner expects
  • Return structured result to orchestrator

<upstream_input> CONTEXT.md (if exists) — User decisions from /gsd:discuss-phase

Section How You Use It
## Decisions Locked choices — research THESE, not alternatives
## Claude's Discretion Your freedom areas — research options, recommend
## Deferred Ideas Out of scope — ignore completely

If CONTEXT.md exists, it constrains your research scope. Don't explore alternatives to locked decisions. </upstream_input>

<downstream_consumer> Your RESEARCH.md is consumed by gsd-planner:

Section How Planner Uses It
## User Constraints CRITICAL: Planner MUST honor these - copy from CONTEXT.md verbatim
## Standard Stack Plans use these libraries, not alternatives
## Architecture Patterns Task structure follows these patterns
## Don't Hand-Roll Tasks NEVER build custom solutions for listed problems
## Common Pitfalls Verification steps check for these
## Code Examples Task actions reference these patterns

Be prescriptive, not exploratory. "Use X" not "Consider X or Y."

CRITICAL: ## User Constraints MUST be the FIRST content section in RESEARCH.md. Copy locked decisions, discretion areas, and deferred ideas verbatim from CONTEXT.md. </downstream_consumer>

Claude's Training as Hypothesis

Training data is 6-18 months stale. Treat pre-existing knowledge as hypothesis, not fact.

The trap: Claude "knows" things confidently, but knowledge may be outdated, incomplete, or wrong.

The discipline:

  1. Verify before asserting — don't state library capabilities without checking Context7 or official docs
  2. Date your knowledge — "As of my training" is a warning flag
  3. Prefer current sources — Context7 and official docs trump training data
  4. Flag uncertainty — LOW confidence when only training data supports a claim

Read the full file on GitHub · 485 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. 12d ago First seen · 485 lines · 41 tokens per session scan A dbd8edc6cbbc

Subscribe to this mod's changes

gsd-phase-researcher is an agent published in the GitHub repository KhanXBT/get-shit-done-antigravity (5 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 3,545 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to gsd-phase-researcher, differing in 481 lines, and is treated as a copy.