Borrowing it
Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dinhnguyenngoc/spec-driven-claude-code/main/.claude/commands/secure.mdgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/secure)<a href="https://agentmods.dev/commands/dinhnguyenngoc/spec-driven-claude-code/secure"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/secure/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/dinhnguyenngoc/spec-driven-claude-code/secure"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/secure.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.00013 | $0.04165 |
| Opus 5.5 | $0.00005 | $0.01666 |
| Sonnet 5.5 | $0.00003 | $0.00833 |
| Haiku 4.5 | $0.00001 | $0.00417 |
Grade A, and why
secure 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/secure — Pre-Development Security Review
"Security by design, not afterthought."
Purpose
Review architecture for security concerns BEFORE writing any code. Identify threats, define security requirements, and establish controls upfront.
Workspace Mode: if the session root declares
Mode: workspace→ resolve the target repo perCLAUDE.md§Workspace Mode before anything else; every path, probe, and gate below is relative to the target repo, and the workspace disk-check applies at the gate.
Scope
This command is DESIGN-LEVEL threat modeling — no code exists yet.
- ✅ STRIDE on architecture, ADR review, security requirements, OWASP Top 10 compliance check
- ❌ NOT: code scanning, dependency audit, SAST, secret-grep — those belong to
/scan(post-development)
If a finding requires reading source code to confirm, defer it to /scan.
Prerequisites
Input files (must exist before /secure starts):
specs/SPEC.md— for asset inventory, data sensitivity, NFRs, and the Permission Matrix (the business authz basis for IDOR / Elevation-of-Privilege threats — the downstream contractspec.md§Permission Matrix declares)architecture/ARCHITECTURE.md+ its Open Questions sectionarchitecture/adr/*.md— every ADR is a design decision with security implications; read them all (brownfield delta: read the ADRs touching the delta surface — see §Brownfield Mode)plans/plan.md— for mitigation → task ID mapping (Phase 3). Required for a per-change run only; a whole-system baseline run (brownfield, no active change-set) legitimately has no plan yet and uses evidence ids / Backlog owners instead — see §Brownfield Mode → Baseline run..claude/rules/security.md— non-negotiables
Boilerplate templates (fixed — the agent fills in data, does not re-author structure):
.claude/templates/STRIDE_TEMPLATE.md— Asset inventory, STRIDE reference, Risk matrix, Threat block, Highest-Risk Surface table, THREAT_MODEL skeleton.claude/templates/OWASP_TEMPLATE.md— OWASP Top 10 (2021) 10-row table, Security Requirements 6-domain checklist, Residual Risks table
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 · 212 lines · 13 tokens per session scan A a6c91978b6e6
secure is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 4,165 once invoked, about $0.0001 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
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
type-coverage
Vérification Couverture des Types Python.
generate-adapter
Erstellt ein Paperclip-Extension-Gerüst (Plugin via create-paperclip-plugin oder Built-in-Adapter).
wayfind
Plan a chunk of work too big for one agent session as a shared decision map: map.md + typed decision tickets in the mega-goal folder, resolved one per session through the kit's own grill/prototype/research machinery, until nothing is left to decide. Then hand off to /kit:spec or a ROADMAP, never straight to execute.
devs-team
Parallel multi-lens critique of a solution design (the active spec if present, else the decision brief). Dispatches 5 engineering lenses, merges findings, reports a verdict. Report-only, never blocks.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode), issue tracker.