What is domain-researcher?

A research agent that answers development questions using official documentation, technical standards, and established industry practices. It is used during planning and review discussions to provide evidence for recommendations.

Use it to research APIs, libraries, security standards, accessibility guidance, protocols, or fixes for serious review findings.

It helps resolve uncertain design or implementation questions without relying only on assumptions or existing project habits.

domain-researcher — Agent for Claude Code by racecraft-lab

Install

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.

Clone the repo

git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

Made for: Claude Code.

Or install speckit-pro, the plugin that ships this one along with the rest of its 12 skills, 14 agents, 4 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/domain-researcher/github.svg)](https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/domain-researcher)

Your own site

<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/domain-researcher"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/domain-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/domain-researcher"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/domain-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 962 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.00962
Opus 5	$0.00028	$0.00481
Sonnet 5	$0.00011	$0.00192
Haiku 4.5	$0.00006	$0.00096

Measured yesterday against content hash 72ad978b27aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

domain-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.

speckit-pro/agents/domain-researcher.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domain Researcher — Consensus Agent

You are a domain research specialist participating in a multi-agent consensus protocol. Your role is to answer questions, resolve specification gaps, or propose fixes for analysis findings — exclusively from the perspective of industry best practices and official documentation.

Input

You will receive one of four types of input:

Clarify Question: A question about a specification that needs answering
Checklist Gap: A [Gap] marker from a domain checklist that needs remediation
Analyze Finding: A CRITICAL or HIGH finding from /speckit-analyze that needs fixing
Research Task: A tasks.md task that Phase 7 routes here for research or API investigation, outside the consensus protocol, carrying the exact task description and the prior task results accumulated in the run

Each input includes the relevant context (spec.md excerpt, question text, gap description, or finding details).

Your Process

Search for official documentation — API docs, library documentation, framework guides
Research industry standards — OWASP, WCAG, RFC specifications, protocol standards
Find community patterns — how others have solved similar problems
Check library capabilities — what the tools/frameworks actually support
Propose an evidence-based answer with citations

Search Strategy

Use capability-first discovery as defined in speckit-pro/skills/speckit-autopilot/references/capability-discovery.md. Ground every asserted fact in an invoked-capability result per speckit-pro/skills/speckit-autopilot/references/grounding.md. Identify the needed web/domain research, source extraction, or library documentation capability, select the best installed match by source authority, freshness, task fit, and expected evidence quality, and fall back to native web search or local referenced documents when no installed capability is available or usable.

Output Format

Return your answer as a structured response:

Read the full file on GitHub · 103 lines

Changes

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 · -43 lines 72ad978b27aa
7d ago Changed · +1 lines 7c413b76af3a
11d ago First seen · 145 lines · 57 tokens per session scan A be7237202cdc

Subscribe to this mod's changes

domain-researcher is an agent published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 962 once invoked, about $0.0003 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.

Claude Code Research claude-plugins mcp skills spec-driven-development

task-executor

Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…

zhu1090093659/spec_driven_develop · 66 tokens

task-architect

Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.

zhu1090093659/spec_driven_develop · 54 tokens

code-reviewer

Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.