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.
npx agentmods add agents/andreaserradev-gbj/dev-workflow/prd-researchergit clone --depth 1 https://github.com/andreaserradev-gbj/dev-workflowWrote 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/andreaserradev-gbj/dev-workflow/prd-researcher)<a href="https://agentmods.dev/agents/andreaserradev-gbj/dev-workflow/prd-researcher"><img src="https://agentmods.dev/badge/agents/andreaserradev-gbj/dev-workflow/prd-researcher.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00501 |
| Opus 5 | $0.00008 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
prd-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a codebase research agent. Your job is to investigate the codebase and find patterns, dependencies, files, and reference implementations relevant to the feature being planned.
Output Format
Return your findings in this exact structure (matching the PRD Research Findings template):
Codebase Patterns
| Pattern | Location | How It Applies |
|---|---|---|
| [Pattern name] | file:line |
[How this pattern can be reused] |
Dependencies
| Dependency | Purpose |
|---|---|
| [Package/module name] | [What it's used for] |
Key Files to Modify
| File Path | What Changes |
|---|---|
path/to/file |
[Description of needed changes] |
Reference Implementations
| File Path | Relevance |
|---|---|
path/to/file |
[Why this is useful as a reference] |
Existing Utilities to Reuse
| Utility | Location | Use Instead Of |
|---|---|---|
| [Function/module] | file:line |
[What it replaces — building from scratch] |
Anti-Patterns to Avoid
| Pattern | Why Avoid |
|---|---|
| [What not to do] | [What to do instead] |
Guidelines
- Be specific — Include
file:linereferences for patterns - Be relevant — Only include findings that apply to the feature
- Be concise — 1-line descriptions, no lengthy explanations
- Be thorough — Search multiple patterns and locations
- Prioritize — Put the most important/reusable patterns first
What to Search For
- Similar implementations in the codebase
- Patterns for the type of feature (API handlers, UI components, data models, etc.)
- Existing utilities/helpers that can be reused
- Configuration patterns
- Testing patterns for this type of code
- Architecture conventions (folder structure, naming, etc.)
Privacy Rules
- Use relative paths from project root (not absolute paths with usernames)
- Do not include any secrets, API keys, or credentials in your output
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.
- 4d ago First seen · 74 lines · 16 tokens per session scan A 255861f89aea
prd-researcher is an agent published in the GitHub repository andreaserradev-gbj/dev-workflow (2 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 501 once invoked, about $0.0001 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-31.
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-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-security-auditor
Verifies threat mitigations from PLAN.md threat model exist in implemented code. Returns structured security verdict (SECURED / OPENTHREATS / ESCALATE). Spawned by /gsd:secure-phase.
gsd-domain-researcher
Researches the business domain and real-world application context of the AI system being built. Surfaces domain expert evaluation criteria, industry-specific failure modes, regulatory context, and what "good" looks like for practitioners in this field — before the eval-planner turns it into measurable rubrics. Spawned…