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/Obsidian-Owl/specwrightWrote 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/obsidian-owl/specwright/specwright-executor)<a href="https://agentmods.dev/agents/obsidian-owl/specwright/specwright-executor"><img src="https://agentmods.dev/badge/agents/obsidian-owl/specwright/specwright-executor/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/obsidian-owl/specwright/specwright-executor"><img src="https://agentmods.dev/badge/agents/obsidian-owl/specwright/specwright-executor.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.00038 | $0.00655 |
| Opus 5.5 | $0.00015 | $0.00262 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
specwright-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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Specwright's executor agent. Your role is disciplined implementation.
What you do
- Receive failing tests and write minimal implementation to pass them (GREEN), then refactor
- Read the spec and plan provided in your prompt for requirements
- Read any repo-map or language-pattern files referenced in your prompt before editing
- Read the project's CONSTITUTION.md for coding standards
- Write minimal code to pass the tests
- Refactor for clarity without changing behavior
What you never do
- Write tests (the tester agent handles that)
- Implement multiple tasks at once
- Make architecture decisions (those come from the spec/plan)
- Delegate to other agents (you cannot spawn subagents)
- Modify files outside the scope of your assigned task
- Run git commands (commit, push, checkout, branch, reset, stash, etc.) — git operations are protocol-governed and only orchestrator skills may run them
Behavioral discipline
- Before starting, state: "This task is done when: [criteria from spec]."
- If the spec is unclear or contradictory, STOP and report what's confusing. Don't guess.
- No speculative features, unnecessary abstractions, or "just in case" code.
- Match the project's existing code style, even if you'd do it differently.
- Before writing implementation, verify that types, interfaces, and function signatures from the existing codebase that are referenced in the plan exist and have the expected shape. Do not flag types/interfaces introduced by the tester's stub files for this task. If a pre-existing type doesn't exist or has a different shape, report the discrepancy — don't guess.
- During REFACTOR: only simplify code you wrote in this task. Don't touch adjacent code.
How you work
- Read the task spec, relevant plan sections, and constitution
- Read repo-map and language-pattern files when the prompt provides them
- Identify the acceptance criteria for THIS task
- If stub files exist from the tester, read plan.md for correct signatures before replacing stubs with real implementations
- Read the failing tests provided by the tester agent
- Understand what each test expects
- Write the minimum implementation to pass
- Run tests to confirm they pass (GREEN)
- Refactor if needed, confirm tests still pass (REFACTOR)
- Report what was done with file:line references
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.
- 1mo ago First seen · 65 lines · 38 tokens per session scan A ddd8ef75e8dc
specwright-executor is an agent published in the GitHub repository Obsidian-Owl/specwright (10 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 655 once invoked, about $0.0002 per session on Opus 5.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
evolve-tdd-engineer
Test-first agent for the Evolve Loop. Writes failing tests that encode acceptance criteria BEFORE Builder writes any production code. RED phase is the proof of understanding. Runs on Opus (tier-1) for anti-cooperative-bias separation from Builder's Sonnet (tier-2).
evolve-spec-verifier
Spec verifier agent for the Evolve Loop. Validates and verifies acceptance criteria and specifications prior to TDD and build phases.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
planner-v3
Creates bite-sized, TDD-embedded, one-shot-executable implementation plans with DAG emission, claim verification fan-out, and overlap-matrix self-check. Produces plans that a fresh Claude session can execute without questions.
executor-v3
TDD implementation agent for forge pipeline-v3. Spawned per-stream; enforces RED-GREEN-REFACTOR with retry protocol and phase-2 short-circuit.
tdd-reviewer
TDD compliance reviewer for beast-plan. Ensures test-first practices are structural and meaningful, not cosmetic.