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-initgit 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.00017 | $0.00395 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
sdlc-init 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 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.
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.
What it actually says
Initialize the current project with the Evo Talos SDLC devkit plugin content.
Arguments: $ARGUMENTS
Run the plugin initializer helper and pass $ARGUMENTS through exactly.
Preferred command:
node "$CLAUDE_PLUGIN_ROOT/scripts/sdlc-init.cjs" $ARGUMENTS
If CLAUDE_PLUGIN_ROOT is unavailable or the helper cannot be found there, locate this plugin directory by finding .claude-plugin/plugin.json or .codex-plugin/plugin.json with "name": "talos", then run:
node "<plugin-root>/scripts/sdlc-init.cjs" $ARGUMENTS
The helper performs these project-local changes:
- Detects the active agent tool from environment signals first, then project markers if needed.
- In Codex, injects
rules/CLAUDE.mdinto the project'sAGENTS.mdinside a managed block. - In Claude Code, injects
CLAUDE.md, mergessettings/original-settings.jsoninto.claude/settings.json, and copies hook scripts into.claude/hooks. - Warns when existing project instruction headings overlap with plugin sections.
- Treats
--target codex|claude|bothas an explicit override for migration or dual-tool setups.
After the helper finishes, summarize the changed files and relay every WARN and ERROR line. If the helper exits nonzero, stop and tell the user which file or conflict needs attention. Do not rerun with --force-hooks unless the user explicitly supplied that flag.
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 · 33 lines · 17 tokens per session scan A d738eacab114
sdlc-init is a command published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 17 tokens to every session and 395 once invoked, about $0.0001 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 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.