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 UnitOneAI/SecuritySkills --skill owasp-top-10-webgit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWrote 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/unitoneai/securityskills/owasp-top-10-web)<a href="https://agentmods.dev/skills/unitoneai/securityskills/owasp-top-10-web"><img src="https://agentmods.dev/badge/skills/unitoneai/securityskills/owasp-top-10-web/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/unitoneai/securityskills/owasp-top-10-web"><img src="https://agentmods.dev/badge/skills/unitoneai/securityskills/owasp-top-10-web.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.00073 | $0.09128 |
| Opus 5 | $0.00036 | $0.04564 |
| Sonnet 5 | $0.00015 | $0.01826 |
| Haiku 4.5 | $0.00007 | $0.00913 |
Grade B, and why
owasp-top-10-web scanned grade B with 3 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 10d 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- No blocking of requests to private/reserved IP ranges (127.0.0.0/8, 10.0.0.0/8, 169.254.169.254, 172.16.0.0/12, 192.168.0.0/16, fd00::/8). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl.*\|.*sh|curl.*\|.*bash|wget.*\|.*sh|pip install.*--trusted-host Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- OS command execution with user-controlled arguments (`exec`, `system`, `child_process.exec`, `os.system`, `subprocess.call` with `shell=True`). How it starts
The opening of the file, as written. The whole thing — 727 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OWASP Top 10:2021 — Web Application Security Review
When to Use
If a target is provided via arguments, focus the review on: $ARGUMENTS
Invoke this skill when:
- Reviewing web application source code for security vulnerabilities.
- Auditing server or framework configurations (e.g., Express, Django, Rails, Spring Boot, ASP.NET).
- A user requests a "security review," "pentest prep," or "OWASP check" against a web application.
- Evaluating pull requests that touch authentication, authorization, input handling, cryptography, or external integrations.
- Assessing a new web project's architecture for secure design principles before implementation begins.
Do not use this skill for mobile-only, IoT firmware, or non-web API reviews — use a domain-specific skill instead.
Context
The OWASP Top 10:2021 is the authoritative awareness document for web application security. It represents broad consensus on the most critical security risks to web applications, derived from CWE data mapped across hundreds of organizations. Each category aggregates multiple CWEs under a unifying risk theme.
This skill operationalizes all ten categories into a repeatable, structured review process suitable for AI-assisted code analysis. Findings are mapped to specific CWEs, rated by severity, and paired with actionable remediation steps.
Process
Step 1 — Scope and Inventory
- Use
Globto enumerate the project structure: source files, configuration files, dependency manifests, and infrastructure-as-code templates. - Identify the technology stack: language, framework, template engine, ORM, authentication library, and deployment target.
- Catalog entry points: routes, controllers, API endpoints, middleware chains, and static asset serving.
- Note dependency manifests (
package.json,requirements.txt,pom.xml,Gemfile.lock,go.sum, etc.) for component analysis.
Step 2 — Category-by-Category Analysis
Evaluate the codebase against each of the ten categories below. For every category, search for the listed detection patterns using Grep and Read, then record findings.
What ships with it
1 file 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.
- 10d ago First seen · 727 lines · 73 tokens per session scan B 9ad620c93944
owasp-top-10-web is a skill published in the GitHub repository UnitOneAI/SecuritySkills (61 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 9,128 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 3 findings (cloud metadata endpoint, makes network calls, 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
audit-security-requirements
Audit the current repository against a security requirements catalog and verify whether each requirement is implemented. Requirement IDs follow your catalog's own naming scheme (e.g. SEC-CSP-1, SCG-HARDENXML, or anything your YAML defines); tagging code with those IDs is optional and not required. Prints open…
review-threat-model
User-facing triage of an existing threat model — an overview-first console over an already-generated threat-model.yaml (backlog by priority, severity mix, worst-case scenarios), then one of three modes. "Just look around" browses findings read-only by severity, security aspect, requirement, or control posture. "Fix or…
ask-threat-model
Answer ANY question about the threat model in this repo — read-only Q&A over the committed threat-model.yaml. The default surface for every natural-language query about the model, however simple: does one exist at all ("is there a threat model here?", "gibt es hier ein bedrohungsmodell?"), how it stands ("how bad is…
export-threat-model
Re-export a finished threat-model.yaml/.md into PDF + HTML + SARIF + pentest-tasks artifacts, or the alpha OWASP Threat Dragon / ThreatAtlas JSON. Standalone post-processing — does not analyze the repo, does not run any agent. SARIF, pentest-tasks and Threat Dragon are derived deterministically from threat-model.yaml…
verify-requirements
Help a developer check the code they just changed against their company security requirements — or, if none are configured, against a built-in best-practices baseline. Scopes to the current diff, dispatches the appsec-reviewer subagent to grade only the triggered requirements, and prints concrete, code-aware guidance…
fix-run-issues
Identify and apply fixes for issues recorded by the previous create-threat-model run. Auto-applies safe fixes with confirmation; prints manual-review guidance for everything else.