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 commands/evolplus/talos/sdlc-loopgit clone --depth 1 https://github.com/evolplus/talosWhat 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.00037 | $0.01143 |
| Opus 5 | $0.00018 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade C, and why
sdlc-loop scanned grade C 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. Dispatch (Steps 4.5 availability, 4.6 journal+local detached worktree for code roles, 5 dispatch), then on each return: validate exit criteria and run the Step 7 finalization transaction: promote validated role-owned How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Orchestrator. Enter Autonomous Execution Loop mode per .claude/rules/autonomous-loop.md §15. Run continuously, dispatching eligible tasks yourself, until a halt condition fires — do NOT yield back to the operator after a single batch.
Arguments (may be empty): $ARGUMENTS
Setup (do this once, before the loop)
-
Parse
$ARGUMENTS:--tier <aggressive|standard|conservative>→ use this as the active workload tier for this run (overrides §13.3 env/SRS resolution for the session). If absent, resolve the tier normally per.claude/rules/workload-tier.md§13.3.--max-iterations <N>→ per-invocation soft cap (§15.6). Default 50.--schedule [cadence]→ after starting the loop, ALSO register a scheduled task using whatever scheduled-task mechanism the host provides (e.g. acreate_scheduled_tasktool in Cowork; cron / an SDK driver under bare Claude Code) whose prompt is exactly/sdlc-loop(carry forward--tier/--max-iterationsbut NOT--schedule, to avoid stacking schedules). Cadence default: hourly (0 * * * *). If no scheduler is available in this environment, say so and fall back to manual continuation rather than erroring. Confirm the registration to the operator with the task id + cadence. Note to the operator: each fire is a fresh run that resumes via §14; a fire that hits a human gate (H1–H4) will halt and re-fire fruitlessly until the gate is resolved, so they may pause the schedule for long-lived gates.
-
Run the §9 pre-flight ONCE: Step 0 (git repo + committer identity — halt with NEEDS_CONTEXT if identity unset), Step 0.5 (root-level
plan-update*.jsonstraggler sweep), Step 0.6 (crash-recovery reconciliation of any surviving dispatch journal per.claude/rules/crash-recovery.md§14). Log the active tier in the start summary.
The loop (repeat until a halt condition)
Each iteration is one §9 cycle. Read project state from disk at the top of every iteration — never from a list you built earlier in this run (.claude/rules/autonomous-loop.md §15.2):
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.
- 2d ago First seen · 36 lines · 37 tokens per session scan C 978ac64f0804
sdlc-loop is a command published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,143 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.