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/codeverbojan/claude-code-kickstart/security-reviewgit clone --depth 1 https://github.com/codeverbojan/claude-code-kickstartWhat 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.00018 | $0.00791 |
| Opus 5 | $0.00009 | $0.00396 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
security-review 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Audits the diff between the working tree and the remote default branch
(origin/HEAD) for security issues. Wraps the built-in review with
preflight checks that fail loudly and explain how to fix common setup
problems — instead of bubbling up cryptic git errors.
1. Preflight — verify git state
Run these checks in order. If any fails, STOP and print the matching "Fix" block to the user verbatim. Do not proceed until the user has fixed the issue.
Check A — is this a git repo?
git rev-parse --is-inside-work-tree
If it fails:
Not a git repository.
/security-reviewdiffs against a remote branch, so it needs a git repo. Eithercdinto a repo, or rungit init && git remote add origin <url>first.
Check B — does the repo have a remote named origin?
git remote get-url origin
If it fails:
No
originremote./security-reviewdiffs againstorigin/HEAD, which requires a remote. Add one with:git remote add origin <your-repo-url> git fetch origin git remote set-head origin --autoIf this repo intentionally has no remote, run a full-tree audit instead by invoking the
security-revieweragent directly.
Check C — is refs/remotes/origin/HEAD set?
git symbolic-ref refs/remotes/origin/HEAD
If it fails with "is not a symbolic ref":
origin/HEADis not set on this repo. This is the most common cause of/security-reviewfailures and happens on repos that weren't freshly cloned. Fix it with one command:git remote set-head origin --autoThis is a local-only, non-destructive bookkeeping change. It asks the remote which branch is default and points the local ref at it. Reverse with
git remote set-head origin --deleteif needed.If
--autofails (remote unreachable, or remote has no default branch), set it explicitly:git remote set-head origin main # or master, develop, etc.
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 · 111 lines · 18 tokens per session scan A 74e5b18afad7
security-review is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 791 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
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
_subagent-discovery
Whenever a command needs to pick a subagent for a task (planning, task generation, or implementation execution). Do not hardcode agent names in command templates. Do not assume a specific agent exists.