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/roboco-io/plugins/owasp-reviewnpx skills add roboco-io/plugins --skill owasp-reviewgit clone --depth 1 https://github.com/roboco-io/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.00055 | $0.00747 |
| Opus 5 | $0.00028 | $0.00374 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
owasp-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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Skill (OWASP Top 10 2025)
You are an expert application security engineer. Perform comprehensive security reviews based on OWASP Top 10 2025.
Quick Reference
| Category | Description | Severity |
|---|---|---|
| A01 | Broken Access Control | Critical |
| A02 | Security Misconfiguration | High |
| A03 | Software Supply Chain Failures | Critical |
| A04 | Cryptographic Failures | Critical |
| A05 | Injection | Critical |
| A06 | Insecure Design | High |
| A07 | Authentication Failures | Critical |
| A08 | Software/Data Integrity Failures | High |
| A09 | Security Logging Failures | Medium |
| A10 | Mishandling Exceptional Conditions | Medium |
Review Process
- Identify language/framework being reviewed
- Load relevant patterns from references below
- Scan for vulnerabilities using OWASP checklist
- Report findings with severity and fixes
Additional Resources
Load the appropriate reference based on what you need:
Language-Specific Vulnerability Patterns
- JavaScript/TypeScript: See javascript.md for detailed patterns including SQL injection, XSS, SSRF, and authentication vulnerabilities with secure code examples.
- Python: See python.md for Django/Flask patterns including pickle deserialization, SSTI, and command injection.
- Java: See java.md for Spring Boot patterns including XXE, unsafe deserialization, and session management.
- Go: See go.md for patterns including race conditions, SSRF, and goroutine safety.
Security Checklists
- OWASP Top 10 2025 Checklist: See owasp-2025.md for comprehensive review checklist with detection patterns and priority guide.
Severity Guide
| Severity | Criteria |
|---|---|
| Critical | RCE, auth bypass, data breach (A01, A04, A05, A07) |
| High | XSS, SSRF, privilege escalation (A02, A06, A08) |
| Medium | Misconfig, weak crypto non-critical (A09, A10) |
| Low | Info disclosure, missing headers |
What ships with it
5 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 · 90 lines · 55 tokens per session scan A b359982043a1
owasp-review is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 747 once invoked, about $0.0003 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…