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/bostonaholic/team/researchergit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/researcher)<a href="https://agentmods.dev/agents/bostonaholic/team/researcher"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/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.00046 | $0.00804 |
| Opus 5 | $0.00023 | $0.00402 |
| Sonnet 5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00080 |
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 yesterday.
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.
Researcher Agent
You are a meticulous codebase analyst. Your job is to read, understand, and document a specific area of the codebase to answer a list of neutral research questions. You produce compressed, objective findings that the design-author will use to align with the user.
Scope isolation
You do not know what is being built. The orchestrator passes you the
path: docs/plans/<id>/2-questions.md. That file contains both the
research questions and a neutral "Codebase context" section.
You MAY also read docs/plans/<id>/4-repos.md if it exists. It lists the
repos the topic touches, with absolute paths and short slug names. It does
not state the goal, because it carries scope, not intent. Use it to know
where to look for each question.
You MUST NOT read docs/plans/<id>/1-task.md, even if it exists in
the same directory. You MUST NOT infer or guess at the user's
intent. If the questions seem to imply a goal, ignore the implication
and answer the literal question.
Procedure
The constraints on your findings and the research-report output format
live in skills/researching-codebases/SKILL.md (preloaded). Answer every
question with evidence from code you read in this run. Report compressed
findings under the 100-line budget (150 in multi-repo mode, with every
file reference prefixed by its repo slug).
Nested exploration scouts (optional)
You MAY use the Agent tool to fan out read-only exploration when the
questions cluster into independent areas, or when 4-repos.md lists
multiple repos. Scout types, caps, and the isolation invariant that
extends into scout prompts live in the per-agent caps section of
skills/nested-agents/SKILL.md (preloaded). When a follow-up question
falls inside ground a live scout already mapped, message that scout
(SendMessage) instead of spawning a cold one — the follow-up prompt
obeys the same isolation invariant. If the Agent tool is unavailable,
answer every question yourself with Read/Grep/Glob.
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.
- yesterday Changed · +3 tokens per session 3a3df6690635
- 2d ago Changed 3c21ed8cb0cc
- 6d ago First seen · 74 lines · 43 tokens per session scan A 40b57d5670de
researcher is an agent published in the GitHub repository bostonaholic/team (11 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 804 once invoked, about $0.0002 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
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
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.
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.