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 skills add tomascupr/sandstorm --skill owasp-top-10git clone --depth 1 https://github.com/tomascupr/sandstormWrote 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/tomascupr/sandstorm/owasp-top-10)<a href="https://agentmods.dev/skills/tomascupr/sandstorm/owasp-top-10"><img src="https://agentmods.dev/badge/skills/tomascupr/sandstorm/owasp-top-10/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/skills/tomascupr/sandstorm/owasp-top-10"><img src="https://agentmods.dev/badge/skills/tomascupr/sandstorm/owasp-top-10.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.00000 | $0.00721 |
| Opus 5.5 | $0.00000 | $0.00288 |
| Sonnet 5.5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
owasp-top-10 scanned grade A with 1 finding 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 2mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- [ ] Command injection via `os.system()`, `subprocess.shell=True` How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OWASP Top 10 Security Audit Checklist
Use this checklist when performing security audits. Check each category systematically against the codebase.
A01:2021 — Broken Access Control
- Missing authorization checks on endpoints
- Insecure direct object references (IDOR)
- Missing function-level access control
- CORS misconfiguration allowing unauthorized origins
- Path traversal via user-controlled file paths
- JWT token manipulation or missing validation
A02:2021 — Cryptographic Failures
- Hardcoded secrets, API keys, or passwords in source
- Weak hashing algorithms (MD5, SHA1 for passwords)
- Missing encryption for sensitive data at rest
- HTTP used instead of HTTPS for sensitive endpoints
- Weak or missing TLS configuration
- Predictable random values for security tokens
A03:2021 — Injection
- SQL injection via string concatenation or f-strings
- Command injection via
os.system(),subprocess.shell=True - XSS via unescaped user input in HTML templates
- LDAP injection in directory queries
- NoSQL injection in MongoDB/DynamoDB queries
- Template injection (Jinja2, Mako, etc.)
A04:2021 — Insecure Design
- Missing rate limiting on authentication endpoints
- No account lockout after failed login attempts
- Missing CSRF protection on state-changing operations
- Lack of input validation at trust boundaries
- Missing re-authentication for sensitive operations
A05:2021 — Security Misconfiguration
- Debug mode enabled in production
- Default credentials still active
- Unnecessary features or services enabled
- Missing security headers (CSP, X-Frame-Options, etc.)
- Verbose error messages exposing stack traces
- Overly permissive file/directory permissions
A06:2021 — Vulnerable and Outdated Components
- Dependencies with known CVEs
- Outdated frameworks or libraries
- Unmaintained or abandoned packages
- Missing lock files (package-lock.json, poetry.lock)
- Using deprecated APIs or functions
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.
- 2mo ago First seen · 85 lines · 0 tokens per session scan A d072ad817e84
owasp-top-10 is a skill published in the GitHub repository tomascupr/sandstorm (450 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 721 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
vibing-orchestrate
A coordinator for splitting independent tasks among separate vibing.nvim chats, a Neovim interface for working with coding agents, and combining their results.
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
adding-config-fields
Patterns for adding, renaming, removing, or retyping fields in DorkOS user config. Use when editing UserConfigSchema, MarketplacesFileSchema, or any conf-backed store — walks the Zod field → defaults → conf migration → docs → test lifecycle end-to-end.
self-testing
E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…
visual-companion
Browser-based visual companion for showing mockups, diagrams, comparisons, and interactive options. Use when the user would understand something better by seeing it than reading it.
marketplace-dev
Develop, validate, and publish DorkOS marketplace packages — agents, plugins, skill-packs, and adapters. Use when creating marketplace items, working in the dork-labs/marketplace repo, or helping users build packages for the personal marketplace.