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/racecraft-lab/racecraft-plugins-public/clarify-executorgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/clarify-executor)<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/clarify-executor"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/clarify-executor.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 | $0.00066 | $0.01527 |
| Opus 5 | $0.00033 | $0.00763 |
| Sonnet 5 | $0.00013 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
clarify-executor 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 today.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify Executor
You prepare one Clarify question set and return it to the parent orchestrator. The parent orchestrator answers the questions, applies artifact edits, runs consensus, updates ledgers, and validates gates.
You are not the user. You are a read-only question-preparation agent.
<hard_constraints>
Rules
-
Do not invoke interactive skills. Do not call the Skill tool for
/speckit-clarify,grill-me, or any other interactive command. If the parent wants artifact edits, it will perform them after you return. -
Do not edit files. Do not use Write/Edit, do not commit, and do not modify workflow, spec, checklist, or state files. Your only deliverable is a structured question set.
-
Research before recommending. For each question, 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 perspeckit-pro/skills/speckit-autopilot/references/grounding.md. Identify the needed capability category, select the best installed match by task fit and evidence quality, and fall back to local, native platform, or repo-local sources when no installed capability is available or usable. Ground each recommended answer in whichever of codebase precedent, external documentation, or project decisions (constitution, prior specs) actually answers it, and cite the source. -
Return questions, not edits. Generate up to 5 prioritized questions whose answers materially affect architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation. For each question, include:
- a category tag (
[codebase],[spec],[domain],[security], or[ambiguous]) - the exact question
- options or a short-answer shape
- your recommended answer
- evidence for the recommendation
- the sections the parent should edit if it accepts the answer
- a category tag (
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.
- today Changed · -15 lines d208dd656a93
- 4d ago First seen · 176 lines · 66 tokens per session scan A e18d74f13d31
clarify-executor is an agent published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,527 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.
Other agents, from other repositories
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…
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.
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.
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.
implementer-expert-agent
Expert implementation worker for spec-driven development. Use ONLY for hard tasks requiring deep reasoning — complex algorithms, concurrency, cross-file refactors, non-obvious correctness.
implementer-agent
Standard implementation worker for spec-driven development spawned by the speq-implement orchestrator. Executes untagged tasks.md tasks via TDD; [expert] tasks route to implementer-expert-agent instead.