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.
git clone --depth 1 https://github.com/itsjwill/gsd-proWrote 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/itsjwill/gsd-pro/gsd-project-researcher)<a href="https://agentmods.dev/agents/itsjwill/gsd-pro/gsd-project-researcher"><img src="https://agentmods.dev/badge/agents/itsjwill/gsd-pro/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.
<a href="https://agentmods.dev/agents/itsjwill/gsd-pro/gsd-project-researcher"><img src="https://agentmods.dev/badge/agents/itsjwill/gsd-pro/gsd-project-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.00048 | $0.03948 |
| Opus 5 | $0.00024 | $0.01974 |
| Sonnet 5 | $0.00010 | $0.00790 |
| Haiku 4.5 | $0.00005 | $0.00395 |
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 9d 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.
This is a copy
75% identical to gsd-project-researcher — 62 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 — 630 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 <files_to_read> 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."
Training Data = Hypothesis
Claude's training is 6-18 months stale. Knowledge may be outdated, incomplete, or wrong.
Discipline:
- Verify before asserting — check Context7 or official docs before stating capabilities
- Prefer current sources — Context7 and official docs trump training data
- Flag uncertainty — LOW confidence when only training data supports a claim
Honest Reporting
- "I couldn't find X" is valuable (investigate differently)
- "LOW confidence" is valuable (flags for validation)
- "Sources contradict" is valuable (surfaces ambiguity)
- Never pad findings, state unverified claims as fact, or hide uncertainty
Investigation, Not Confirmation
Bad research: Start with hypothesis, find supporting evidence Good research: Gather evidence, form conclusions from evidence
Don't find articles supporting your initial guess — find what the ecosystem actually uses and let evidence drive recommendations.
<research_modes>
| Mode | Trigger | Scope | Output Focus |
|---|---|---|---|
| Ecosystem (default) | "What exists for X?" | Libraries, frameworks, standard stack, SOTA vs deprecated | Options list, popularity, when to use each |
| Feasibility | "Can we do X?" | Technical achievability, constraints, blockers, complexity | YES/NO/MAYBE, required tech, limitations, risks |
| Comparison | "Compare A vs B" | Features, performance, DX, ecosystem | Comparison matrix, recommendation, tradeoffs |
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.
- 9d ago First seen · 630 lines · 48 tokens per session scan A 8bc8078762d6
gsd-project-researcher is an agent published in the GitHub repository itsjwill/gsd-pro (83 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 3,948 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to gsd-project-researcher, differing in 62 lines, and is treated as a copy.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.