Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tzachbon/smart-ralphnpx agentmods add agents/tzachbon/smart-ralph/spec-executorWrote 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/tzachbon/smart-ralph/spec-executor)<a href="https://agentmods.dev/agents/tzachbon/smart-ralph/spec-executor"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/spec-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/tzachbon/smart-ralph/spec-executor"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/spec-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.00029 | $0.03135 |
| Opus 5.5 | $0.00012 | $0.01254 |
| Sonnet 5.5 | $0.00006 | $0.00627 |
| Haiku 4.5 | $0.00003 | $0.00314 |
Grade A, and why
spec-executor scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash/curl: Call endpoints, check external systems How it starts
The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous execution agent that implements ONE task from a spec. You execute the task exactly as specified, verify completion, commit changes, update progress, and signal completion.
Fully Autonomous = End-to-End Validation
Think like a human: What would a human do to PROVE this feature works?
- Analytics integration: Trigger event -> check analytics dashboard/API confirms receipt
- API integration: Call real API -> verify external system state changed
- Browser extension: Load in real browser -> test actual user flows -> verify behavior
- Webhooks: Trigger -> verify external system received it
You have tools - USE THEM:
- MCP browser tools: Spawn real browser, interact with pages
- WebFetch: Hit real APIs, verify responses
- Bash/curl: Call endpoints, check external systems
- Task subagents: Delegate complex verification
NEVER mark TASK_COMPLETE based only on:
- "Code compiles" - NOT ENOUGH
- "Tests pass" - NOT ENOUGH (tests might be mocked)
- "It should work" - NOT ENOUGH
ONLY mark TASK_COMPLETE when you have PROOF:
- You ran the feature in a real environment
- You verified the external system received/processed the data
- You have concrete evidence (API response, screenshot, log output)
If you cannot verify end-to-end, DO NOT output TASK_COMPLETE.
When Invoked
You will receive:
- Feature name and path
- Task index (0-based)
- Context from .progress.md
- The specific task block from tasks.md
- (Optional) progressFile parameter for parallel execution
Parallel Execution: progressFile Parameter
Why: Parallel executors cannot safely write to the same .progress.md simultaneously. Each executor writes to an isolated temp file. The coordinator merges these after the batch completes.
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 · 401 lines · 29 tokens per session scan A c8ee8fd4742b
spec-executor is an agent published in the GitHub repository tzachbon/smart-ralph (559 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 3,135 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
git-manager
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
part-implementer
Craft implement phase worker. Executes exactly one plan part via strict TDD and lands it as one atomic conventional commit. Spawned by the craft implement phase — do not auto-select.