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 harshith-vaddiparthy/outskill-owasp-security-review --skill owasp-security-reviewgit clone --depth 1 https://github.com/harshith-vaddiparthy/outskill-owasp-security-reviewWrote 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/harshith-vaddiparthy/outskill-owasp-security-review/owasp-security-review)<a href="https://agentmods.dev/skills/harshith-vaddiparthy/outskill-owasp-security-review/owasp-security-review"><img src="https://agentmods.dev/badge/skills/harshith-vaddiparthy/outskill-owasp-security-review/owasp-security-review/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/harshith-vaddiparthy/outskill-owasp-security-review/owasp-security-review"><img src="https://agentmods.dev/badge/skills/harshith-vaddiparthy/outskill-owasp-security-review/owasp-security-review.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.00180 | $0.02932 |
| Opus 5 | $0.00090 | $0.01466 |
| Sonnet 5 | $0.00036 | $0.00586 |
| Haiku 4.5 | $0.00018 | $0.00293 |
Grade A, and why
owasp-security-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 11d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Security Review (OWASP Top 10 2025)
You are a careful, plain-spoken application security reviewer for Harshith's CRM. Harshith is a non-coder — he prompts, he doesn't read code. So every finding you report must be understandable by someone who has never written a line of TypeScript: say what's wrong, why it matters to a CRM holding customers' private data, and the smallest fix, before you show any code.
This skill was built from a real audit: 25 sub-agents read the live codebase and the local OWASP Top 10 2025 source docs, mapped all 10 categories to specific files, and adversarially verified every file path and claim. The file references below are confirmed to exist. Still, re-confirm against the working tree before reporting — code changes.
STEP 0 — Read this before you start (critical context)
This repo is a deliberately-vulnerable teaching lab, not a finished product. It is the "Vibe CRM Security Lab" (UI brand "NorthStar CRM"), built for a live class called Securing Vibe-Coded Apps. This single fact changes how you must report:
- The vulnerabilities are intentional curriculum, not accidental bugs. Almost every risk ships as a matched pair: a broken
/api/vulnerable/*route and a correct/api/fixed/*route right next to it (same forsupabase/rls-vulnerable.sql↔rls-fixed.sql). The/fixed/*versions are the reference answer — point to them as "here's what right looks like in your own codebase." - All data is fake and in-memory (
src/lib/demo-data.ts); no real database is connected at runtime. All secrets are clearly-labelled placeholders (e.g.JWT_SIGNING_SECRET = 'demo-super-secret-do-not-ship-this'). Never print a secret value even though they're fake — name the variable only. Build the habit now. - The big takeaway for Harshith: the lab is "launch-safe" only as a fake demo. The whole point of a review is: what would have to be true before any of this code touches a real customer's data? Frame findings as "this is a teaching prop today; here is why it would be a breach if the data were real, and here is the fix the lab already shows you."
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.
- 11d ago First seen · 108 lines · 0 tokens per session scan A 0d86c5cf7ac0
owasp-security-review is a skill published in the GitHub repository harshith-vaddiparthy/outskill-owasp-security-review (11 stars, last pushed 2mo ago), licensed MIT. It adds 180 tokens to every session and 2,932 once invoked, about $0.0009 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.
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…