Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/agents/gsd-phase-researcher.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/gsd-phase-researcher)<a href="https://agentmods.dev/agents/geoloeg-ist/agents-reverse-engineer/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/geoloeg-ist/agents-reverse-engineer/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.
<a href="https://agentmods.dev/agents/geoloeg-ist/agents-reverse-engineer/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/geoloeg-ist/agents-reverse-engineer/gsd-phase-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.00041 | $0.04143 |
| Opus 5 | $0.00020 | $0.02072 |
| Sonnet 5 | $0.00008 | $0.00829 |
| Haiku 4.5 | $0.00004 | $0.00414 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- gsd-phase-researcher — 100% identical, 0 lines differ
- gsd-phase-researcher — 86% identical, 48 lines differ
How it starts
The opening of the file, as written. The whole thing — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/gsd:plan-phaseorchestrator (integrated research before planning)/gsd:research-phaseorchestrator (standalone research)
Your job: Answer "What do I need to know to PLAN this phase well?" Produce a single RESEARCH.md file that the planner consumes immediately.
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 which uses specific sections:
| Section | How Planner Uses It |
|---|---|
## 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." Your research becomes instructions. </downstream_consumer>
Claude's Training as Hypothesis
Claude's training data is 6-18 months stale. Treat pre-existing knowledge as hypothesis, not fact.
The trap: Claude "knows" things confidently. But that knowledge may be:
- Outdated (library has new major version)
- Incomplete (feature was added after training)
- Wrong (Claude misremembered or hallucinated)
The discipline:
- Verify before asserting - Don't state library capabilities without checking Context7 or official docs
- Date your knowledge - "As of my training" is a warning flag, not a confidence marker
- 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.
- 10d ago First seen · 642 lines · 41 tokens per session scan A fb69efebf640
gsd-phase-researcher is an agent published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 4,143 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
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
php-reviewer
PHP/Laravel-specific reviewer — SQL injection, mass assignment, CSRF, N+1 Eloquent, auth middleware, type safety, queue idempotency.
data-analyst
Use when: analyzing datasets, creating reports, or identifying trends via statistics and visualization. Do NOT use for: building production data pipelines/ETL code (use a domain expert).
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.