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 ashermahonin/agentic-skills --skill security-owasp-webgit clone --depth 1 https://github.com/ashermahonin/agentic-skillsWrote 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/ashermahonin/agentic-skills/security-owasp-web)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/security-owasp-web"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/security-owasp-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/ashermahonin/agentic-skills/security-owasp-web"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/security-owasp-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.00071 | $0.00706 |
| Opus 5 | $0.00036 | $0.00353 |
| Sonnet 5 | $0.00014 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
security-owasp-web 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 9d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security: OWASP Web Top 10
Purpose
Review a web, API, or mobile-backend surface against the current OWASP categories. Give each applicable category a status backed by code, configuration, or test evidence, then assign remediation and residual risk.
Scope and evidence
- Read
references/owasp-web-top10.md. - Pull the platform matrix from
platform-detectorand the architecture views fromarchitecture-review. - Pull dependency manifests, CI configs, IAM/RBAC definitions, auth flows, and observability surfaces. Read-only.
- Use Context7 MCP to confirm current OWASP wording and any framework's current security guidance (Spring, Django, FastAPI, Express, Rails, Next.js, Phoenix, etc.).
Assessment
- For each Top 10 category, collect evidence: route to the relevant files/configs without writing.
- Mark per-category status: Pass, Concern, Fail, Out-of-scope.
- For Concern/Fail, name: file/config path, what is wrong, blast radius, exploit path sketch, mitigation, owner, and verification test.
- Cross-check with
security-secrets,cve-zero-day-scanner, andinfrastructure-as-codefor shared concerns (secrets, dependencies, IAM). - Produce a remediation plan ordered by exploit risk × ease of fix.
- Hand off to
service-implementationfor fixes andqa-evalfor security test cases.
Safety rules
- Use Context7 MCP for the current OWASP categories, definitions, and framework-specific guidance. Treat
references/owasp-web-top10.mdas a local checklist, not the authority of record. - Keep a decision trace: source documents, framework version, what was checked, what was not checked, and why.
- Refuse to "approve" a category without a named artifact and verification test.
- Escalate before authorizing a release with any unmitigated High finding.
Security record
- Per-category status table (Pass/Concern/Fail/Out-of-scope) with evidence paths
- Findings register: severity, exploit sketch, mitigation, owner, verification test
- Remediation plan ordered by risk × ease
- Cross-links to
security-secrets,cve-zero-day-scanner,infrastructure-as-code - Release gate verdict: Go / Conditional / Hold
What ships with it
2 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.
- 9d ago First seen · 57 lines · 71 tokens per session scan A 5bac2781a2bd
security-owasp-web is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 16d ago), licensed MIT. It adds 71 tokens to every session and 706 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…