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/caiaffa/claude-code-ultimate-engineering-system/security-reviewnpx skills add caiaffa/claude-code-ultimate-engineering-system --skill security-reviewgit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWrote 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/skills/caiaffa/claude-code-ultimate-engineering-system/security-review)<a href="https://agentmods.dev/skills/caiaffa/claude-code-ultimate-engineering-system/security-review"><img src="https://agentmods.dev/badge/skills/caiaffa/claude-code-ultimate-engineering-system/security-review.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00467 |
| Opus 5 | $0.00013 | $0.00234 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 4d 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
Mission
Catch exploitable weaknesses early and improve security posture with practical, auditable controls.
When to use
- Adding endpoints or auth flows.
- Handling files, URLs, secrets, or external integrations.
- Reviewing IAM or service permissions.
- Validating logging and data exposure.
Handoff
- Receives from: code-reviewer (flagged concern) or backend-platform-engineer (new feature with auth/data).
- Hands off to: release-commander (if security changes need careful rollout).
OWASP-aligned checklist
- Authentication — is identity verified correctly? token validation? session management?
- Authorization — is access checked at every layer? (not just UI/controller)
- Injection — SQL, NoSQL, command, LDAP, XSS, template injection?
- Data exposure — PII in logs? secrets in config? sensitive fields in API responses?
- Secret handling — hardcoded? rotatable? scoped? auditable?
- File/URL handling — path traversal? SSRF? unrestricted upload?
- Rate limiting — brute force protection? abuse protection?
- Dependencies — known vulnerabilities? supply chain risk?
- Permissions — least privilege? overly broad IAM?
- Audit trail — who did what, when? tamper-resistant?
Red flags — block deploy
- Secrets in code, config files, or logs.
- SQL string concatenation (even with "trusted" input).
- Missing auth check on any mutation endpoint.
- File upload without type/size validation.
- Internal service endpoint exposed without network restriction.
*in IAM policies.
Output format
- Security summary (risk level: critical / high / moderate / low)
- Critical risks (must fix before deploy)
- High risks (fix in current sprint)
- Moderate risks (fix soon, track in backlog)
- Hardening recommendations (nice to have)
- Trust boundary diagram (who trusts whom)
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.
- 4d ago First seen · 46 lines · 25 tokens per session scan A 426f451b923d
security-review is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 467 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-30.
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…