Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AratKruglik/claude-sdlc/plugin install sdlcWrote 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/aratkruglik/claude-sdlc/security-init)<a href="https://agentmods.dev/commands/aratkruglik/claude-sdlc/security-init"><img src="https://agentmods.dev/badge/commands/aratkruglik/claude-sdlc/security-init/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/aratkruglik/claude-sdlc/security-init"><img src="https://agentmods.dev/badge/commands/aratkruglik/claude-sdlc/security-init.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.00043 | $0.01544 |
| Opus 5.5 | $0.00017 | $0.00618 |
| Sonnet 5.5 | $0.00009 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
security-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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc:security-init
One-time (re-runnable) command that writes stack-specific security rules into .claude/security-patterns.yaml and .claude/claude-security-guidance.md in the current project. These files are read automatically by the security-guidance plugin — it only reads from the project's .claude/ directory, never from plugin install paths.
Run this command after installing security-guidance, when changing stack plugins, or when updating the marketplace (re-running regenerates the managed block only).
Prerequisites
security-guidance@claude-plugins-officialshould be installed and active. If it is not installed, this command still materializes the files (they will be ready when the plugin is installed later) — it prints a reminder at the end.- The current directory must be a project root (contains
.claude/or the command creates it).
Arguments
--dry-run: print what would be written without modifying any files.
Execution (script-first)
Run one Bash call and relay its output; the managed-block idempotency, the dedupe by rule_name, the skip-without-markers warning and the plugin-presence reminder below are all implemented in it:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/security-init.sh" --repo . [--dry-run]
Development checkout fallback: bash plugins/sdlc/scripts/security-init.sh --repo . --dev-root .. You never merge YAML yourself; the algorithm below documents what the script does and is the fallback only when jq is missing (exit 3).
Algorithm
1. Detect active stack plugins
Same detection logic as /sdlc:list-stacks — find all installed stack.md files and evaluate their detect rules against the current working directory. Collect the winning plugin(s). Always include:
sdlccore (base patterns apply to every project)js-foundation(if any JS/TS stack is active)
2. Collect security-patterns fragments
For each active plugin (sdlc core first, then js-foundation, then stack plugins in priority order):
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 Changed · +1 lines 123c0edba1ea
- 11d ago Changed · +10 lines 9dba23aa111b
- 1mo ago First seen · 153 lines · 43 tokens per session scan A 22a2d1616392
security-init is a command published in the GitHub repository AratKruglik/claude-sdlc (53 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,544 once invoked, about $0.0002 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-09-03.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.