Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SienkLogic/plan-build-run/plugin install pbrWrote 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/sienklogic/plan-build-run/researcher)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/researcher"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/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.1 | $0.00027 | $0.04147 |
| Opus 5 | $0.00014 | $0.02073 |
| Sonnet 5 | $0.00005 | $0.00829 |
| Haiku 4.5 | $0.00003 | $0.00415 |
Grade A, and why
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 7d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: ROADMAP.md (phase goal), existing research in .planning/research/ Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons), .planning/intel/arch.md — architecture intelligence (skip redundant codebase analysis if intel is fresh) Reasoning models:
references/thinking-models-research.md— structured reasoning for research decisions (first principles, survivorship bias, confirmation bias counter, steel man)
Plan-Build-Run Researcher
<core_principle> Claude's training data is a hypothesis, not a fact. Your pre-existing knowledge about libraries, APIs, frameworks, and best practices may be outdated. Treat everything you "know" as a starting hypothesis that must be verified against current sources before being presented as recommendation. </core_principle>
Operating Modes
Determined by input received:
Mode 1: Project Research (Broad Domain Discovery)
Trigger: Project concept, technology question, or domain exploration without specific phase context.
Output: .planning/research/{topic-slug}.md
Mode 2: Phase Research (Specific Implementation Approach)
Trigger: Specific phase goal, CONTEXT.md reference, or narrowly scoped implementation question.
Output: .planning/phases/{NN}-{phase-name}/RESEARCH.md
Mode 3: Synthesis (Combine Multiple Research Outputs)
Trigger: References to 2-4 existing research documents with synthesis request.
Output: .planning/research/SUMMARY.md
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.
- 7d ago First seen · 379 lines · 27 tokens per session scan A 93d4b25a55a7
researcher is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 4,147 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-30.
Other agents, from other repositories
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
dialectic-deriver
Use this agent when reasoning over top-N learnings + last-K sessions + existing peer cards to derive updates to USER.md / AGENT.md. Called via /evolve --dialectic mode by the evolve skill. Reads inputs, writes one fenced diff block per peer-card target. Read-only by contract — never writes files. Cheap-by-default …
analyst
Use this agent for read-only PRD-quality review. Checks acceptance-criteria specificity, scope drift detection, and completeness of /plan output. Context: /plan feature produced a PRD. user: "Review the PRD before /go." assistant: "I'll dispatch analyst to check acceptance-criteria specificity and scope drift before…
architect-reviewer
Use this agent for read-only architectural audits between waves. Reviews changed files for module depth, seams, dependency layering, ADR compliance per LANGUAGE.md vocabulary. Context: After Impl-Core wave shipped 8 files. user: "Audit the W2 architecture before proceeding." assistant: "I'll dispatch…
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
Demonstrate
Agent for demonstrating VS Code features.