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/markmocasa-boop/n8n-mcp-czlonWrote 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/markmocasa-boop/n8n-mcp-czlon/gsd-phase-researcher)<a href="https://agentmods.dev/agents/markmocasa-boop/n8n-mcp-czlon/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/markmocasa-boop/n8n-mcp-czlon/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/markmocasa-boop/n8n-mcp-czlon/gsd-phase-researcher"><img src="https://agentmods.dev/badge/agents/markmocasa-boop/n8n-mcp-czlon/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 11d 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
100% identical to gsd-phase-researcher — 0 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 — 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.
- 11d ago First seen · 642 lines · 41 tokens per session scan A fb69efebf640
gsd-phase-researcher is an agent published in the GitHub repository markmocasa-boop/n8n-mcp-czlon (0 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. It is 100% identical to gsd-phase-researcher, differing in 0 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.