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 skills/evolplus/talos/sdlc-initnpx skills add evolplus/talos --skill 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.00079 | $0.00743 |
| Opus 5 | $0.00039 | $0.00371 |
| Sonnet 5 | $0.00016 | $0.00149 |
| Haiku 4.5 | $0.00008 | $0.00074 |
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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Init
Purpose
Codex plugins do not expose Claude-style slash commands from commands/.
This skill is the Codex command shim for /sdlc-init.
Use it when the operator asks to initialize or refresh a project with the Evo Talos kit.
Invocation
- Treat the user's message after
sdlc-initor/sdlc-initas arguments. - Resolve the plugin root from this skill directory:
- this file lives at
skills/sdlc-init/SKILL.md; - the plugin root is two directories up.
- this file lives at
- Run the helper:
node <plugin-root>/scripts/sdlc-init.cjs <arguments>
Do not rely on CLAUDE_PLUGIN_ROOT in Codex. That variable is for Claude Code
slash commands and may not exist in Codex.
Supported Arguments
--target codex- override auto-detection and injectAGENTS.mdonly.--target claude- override auto-detection and writeCLAUDE.md,.claude/settings.json, and.claude/hooks.--target both- override auto-detection and write both Codex and Claude instruction targets.--dry-run- prints planned changes without writing files.--force-hooks- backs up conflicting Claude hook files under.claude/backups/sdlc-init-<timestamp>/hooks/, then replaces them.--skip-agents- skip instruction injection.--skip-settings- skip Claude settings merge.--skip-hooks- skip Claude hook copy.--project <path>- initialize a project root other than the current working directory.
Behavior
The helper performs project-local changes only:
- Detects the active agent tool from environment signals first, then project markers if needed.
- In Codex, injects the plugin contract from
rules/CLAUDE.mdinto the project'sAGENTS.mdinside a managed block. - In Claude Code, injects
CLAUDE.md, merges.claude/settings.json, and copies.claude/hooks. - Warns when existing project instruction headings overlap with plugin sections.
- Uses
--targetonly as an explicit override for unusual migration or dual-tool setups.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 79 tokens per session scan A 30b9ce37a09f
sdlc-init is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 79 tokens to every session and 743 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…