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/tzachbon/smart-ralphWrote 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/commands/tzachbon/smart-ralph/implement)<a href="https://agentmods.dev/commands/tzachbon/smart-ralph/implement"><img src="https://agentmods.dev/badge/commands/tzachbon/smart-ralph/implement/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/commands/tzachbon/smart-ralph/implement"><img src="https://agentmods.dev/badge/commands/tzachbon/smart-ralph/implement.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.00004 | $0.09022 |
| Opus 5.5 | $0.00002 | $0.03609 |
| Sonnet 5.5 | $0.00001 | $0.01804 |
| Haiku 4.5 | $0.00000 | $0.00902 |
Grade A, and why
implement 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 — 1,122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Execution
You are starting the task execution loop.
Determine Active Feature
- Read
.specify/.current-featureto get active feature (format:<id>-<name>) - If file missing or empty: error "No active feature. Run /speckit:start first."
Validate Prerequisites
- Check
.specify/specs/$feature/directory exists - Check
.specify/specs/$feature/tasks.mdexists. If not: error "Tasks not found. Run /speckit:tasks first."
Parse Arguments
From $ARGUMENTS:
- --max-task-iterations: Max retries per task (default: 5)
- --recovery-mode: Enable iterative failure recovery (default: false). When enabled, failed tasks trigger automatic fix task generation instead of stopping.
Commit Uncommitted Spec Files
Before starting execution, check if spec files are uncommitted:
git status --porcelain .specify/specs/$feature/
If uncommitted files exist, commit them:
git add .specify/specs/$feature/
git commit -m "chore(speckit): commit spec files before implementation"
This ensures spec files are tracked before task execution begins.
Initialize Execution State
- Count total tasks in tasks.md (lines matching
- [ ]or- [x]) - Count already completed tasks (lines matching
- [x]) - Set taskIndex to first incomplete task
- Read featureId and name from feature directory name (format:
<id>-<name>)
Write .specify/specs/$feature/.speckit-state.json:
{
"featureId": "<3-digit id>",
"name": "<feature-name>",
"basePath": ".specify/specs/<id>-<name>",
"phase": "execution",
"taskIndex": <first incomplete>,
"totalTasks": <count>,
"taskIteration": 1,
"maxTaskIterations": <parsed from --max-task-iterations or default 5>,
"globalIteration": 1,
"maxGlobalIterations": 100,
"awaitingApproval": false,
"recoveryMode": <true if --recovery-mode flag present, false otherwise>,
"maxFixTasksPerOriginal": 3,
"fixTaskMap": {}
}
Start Execution
After writing the state file, output the coordinator prompt below. This starts the execution loop. The stop-hook will continue the loop by outputting continuation prompts until all tasks are complete.
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 · 1,122 lines · 4 tokens per session scan A ef901e46c9bb
implement is a command published in the GitHub repository tzachbon/smart-ralph (559 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 9,022 once invoked, about $0.0000 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-30.
Other commands, from other repositories
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
milestone-list
PitWay: List every milestone with a concise one-line status.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…