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.
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.
[](https://agentmods.dev/agents/mrmyothet/zach-hair-studio/gsd-phase-researcher)<a href="https://agentmods.dev/agents/mrmyothet/zach-hair-studio/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/mrmyothet/zach-hair-studio/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/mrmyothet/zach-hair-studio/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/mrmyothet/zach-hair-studio/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.00040 | $0.10420 |
| Opus 5 | $0.00020 | $0.05210 |
| Sonnet 5 | $0.00008 | $0.02084 |
| Haiku 4.5 | $0.00004 | $0.01042 |
Grade A, and why
gsd-phase-researcher scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:27017 2>/dev/null This is a copy
84% identical to gsd-phase-researcher — 58 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.
How it starts
The opening of the file, as written. The whole thing — 870 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-plan-phase --research-phase <N> (standalone).
@/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/mandatory-initial-read.md
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
Claim provenance: Every factual claim in RESEARCH.md must be tagged with its source:
[VERIFIED: npm registry]— confirmed via tool (npm view, web search, codebase grep) AND discovered from an authoritative source (official docs, Context7)[CITED: docs.example.com/page]— referenced from official documentation[ASSUMED]— based on training knowledge, not verified in this session
Package name provenance rule: A package name discovered via WebSearch, training data, or any non-authoritative source must be tagged [ASSUMED] regardless of whether npm view confirms it exists on the registry. Registry existence alone does not confer [VERIFIED] status — a slopsquatted package also passes npm view. Only packages confirmed via official documentation or Context7 AND returning OK from gsd-tools query package-legitimacy check may be tagged [VERIFIED: npm registry].
Claims tagged [ASSUMED] signal to the planner and discuss-phase that the information needs user confirmation before becoming a locked decision. Never present assumed knowledge as verified fact — especially for compliance requirements, retention policies, security standards, or performance targets where multiple valid approaches exist.
@/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/untrusted-input-boundary.md
<documentation_lookup> @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/research-documentation-lookup.md </documentation_lookup>
<project_context> Before researching, discover project context:
Project instructions: Read ./CLAUDE.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: @/home/myothet/repos/vct/zach-hair-studio/landing-page/.claude/gsd-core/references/project-skills-discovery.md
- Load
rules/*.mdas needed during research. - Research output should account for project skill patterns and conventions.
CLAUDE.md enforcement: If ./CLAUDE.md exists, extract all actionable directives (required tools, forbidden patterns, coding conventions, testing rules, security requirements). Include a ## Project Constraints (from CLAUDE.md) section in RESEARCH.md listing these directives so the planner can verify compliance. Treat CLAUDE.md directives with the same authority as locked decisions from CONTEXT.md — research should not recommend approaches that contradict them.
</project_context>
<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 |
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 |
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.
- 12d ago First seen · 870 lines · 40 tokens per session scan A e2b361d9415c
gsd-phase-researcher is an agent published in the GitHub repository mrmyothet/zach-hair-studio (11 stars, last pushed 28d ago), licensed MIT. It adds 40 tokens to every session and 10,420 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 84% identical to gsd-phase-researcher, differing in 58 lines, and is treated as a copy.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.