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/sembraniteam/claude-plugins/secure-code-reviewnpx skills add sembraniteam/claude-plugins --skill secure-code-reviewgit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWhat 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.00109 | $0.03526 |
| Opus 5 | $0.00055 | $0.01763 |
| Sonnet 5 | $0.00022 | $0.00705 |
| Haiku 4.5 | $0.00011 | $0.00353 |
Grade A, and why
secure-code-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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Code Review Methodology
This skill provides the checklist, CWE mapping, and report template used by all security-auditor commands.
Additional Resources
references/baseline-suppression.md—.security-audit-baseline.jsonformat, matching rules, and how to fold suppressions into a report. Read this whenever a project has a baseline file, or when the user asks to suppress/accept a finding.references/sarif-output.md— SARIF 2.1.0 structure, field rules, and severity mapping for/audit-report --sarif. Read this only when generating SARIF output.references/remediation-protocol.md— Fix manifest schema, reviewer verdict values, the one-retry rule, and per-CWE minimal-fix examples used bysecurity-fixerandfix-reviewer. Read this when fixing or verifying findings (/audit-fix,/audit-verify), not during a plain audit.
OWASP Top 10 (2025) Checklist + Extended Categories
Work through each category. Mark each as: ✓ checked, ⚠ findings, or N/A (not applicable to this codebase).
OWASP Top 10
| # | Category | Key checks |
|---|---|---|
| A01 | Broken Access Control | Missing authz checks, IDOR, path traversal, CORS misconfiguration, privilege escalation, SSRF (outbound HTTP with user-controlled URL, missing allowlist, cloud metadata endpoint exposure) |
| A02 | Security Misconfiguration | Default credentials, unnecessary features enabled, verbose errors, missing security headers, overly-permissive cloud storage policies |
| A03 | Software Supply Chain Failures | Dependencies with known CVEs (verified via MCP, never from memory), untrusted/typosquatted packages, unsigned or unverified build artifacts/container images, missing dependency pinning or SBOM |
| A04 | Cryptographic Failures | Sensitive data in plaintext, weak algorithms, static keys/IVs, missing TLS |
| A05 | Injection | SQL, NoSQL, OS command, LDAP, XPath, template, expression language |
| A06 | Insecure Design | Missing rate limiting, insecure direct object references in design, trust boundary violations |
| A07 | Authentication Failures | Weak passwords, missing MFA support, insecure session management, credential stuffing exposure |
| A08 | Software or Data Integrity Failures | Unsigned updates/plugins, insecure deserialization, missing checksums/digital signatures, absent tamper-detection on critical data |
| A09 | Security Logging & Alerting Failures | No audit trail for sensitive ops, PII logged, log injection, missing alerting on suspicious activity |
| A10 | Mishandling of Exceptional Conditions | Verbose error messages leaking internals, fail-open logic on exception/error paths, unhandled timeouts, generic catch-alls masking security failures |
What ships with it
3 files 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 · 247 lines · 109 tokens per session scan A 95f002b1fc8b
secure-code-review is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 29d ago), licensed MIT. It adds 109 tokens to every session and 3,526 once invoked, about $0.0005 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…