owasp-audit

owasp-audit is a cursor rule for Cursor from briiirussell/cybersecurity-skills. It costs 197 tokens per session (12,289 once invoked), scanned A, original, MIT.

A source-code security review organised around the OWASP Top 10, a widely used list of common web-application risks.

In plain words
What is it for?
Use it to inspect an application's entry points, data flows, authentication boundaries, and code against the 2021 OWASP Top 10 categories.
Why use it?
It provides a systematic way to look for issues such as missing access checks, injection, unsafe cryptography, weak authentication, and security misconfiguration.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to inspect an application's entry points, data flows, authentication boundaries, and code against the 2021 OWASP Top 10 categories.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/briiirussell/cybersecurity-skills/owasp-audit
Install

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.

Clone the repo
git clone --depth 1 https://github.com/briiirussell/cybersecurity-skills

Made for: Cursor.

Wrote 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.

agentmods badge for owasp-audit

README.md
[![agentmods](https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/owasp-audit/github.svg)](https://agentmods.dev/rules/briiirussell/cybersecurity-skills/owasp-audit)
Your own site
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/owasp-audit"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/owasp-audit/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.

agentmods 80×15 button for owasp-audit

Your own site · 80×15
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/owasp-audit"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/owasp-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 197 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,289 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00197 $0.12289
Opus 5.5 $0.00079 $0.04916
Sonnet 5.5 $0.00039 $0.02458
Haiku 4.5 $0.00020 $0.01229

Measured today against content hash 790b7cbcbbde, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

owasp-audit 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 today.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Only audit code the user owns or is authorized to review. Any live check (for example `curl -I` against a deployed
adapters/cursor/owasp-audit.mdc · 475 lines

How it starts

The opening of the file, as written. The whole thing — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OWASP Audit — Source Code Security Review

Perform a systematic security audit of application source code against the OWASP Top 10:2025. Every candidate is traced, then independently challenged, before it becomes a finding. Coverage is recorded per surface and trust boundary, so "clean" means someone actually read the code.

Cross-references:

  • api-audit for a surface-driven pass over every API endpoint (shares the recon, verification, and orchestration references)
  • web-pentest "Combined white-box + black-box mode" when you have both the source and a running instance you're authorized to test
  • business-logic-testing to prove race conditions and logic flaws dynamically (A06)
  • dependency-audit for the full A03 supply-chain picture; secrets-audit for leaked credentials
  • threat-modeling for the principal / trust-boundary vocabulary used in recon
  • finding-triage to take a single finding from this report to a defensible disposition

Authorization and Mode

Only audit code the user owns or is authorized to review. Any live check (for example curl -I against a deployed origin) needs the same authorization for that host and stays non-destructive.

Pick the mode before starting:

  • Guidance (default): a question, a single file, or "how do I secure X". Answer directly. Findings still follow the verdict rules below. No ledger required.
  • Full audit: the user explicitly asks to audit or security-review a codebase, a release, or a PR. Run the full workflow below.
  • Diff / PR-scoped: the user wants a branch, PR, or commit range reviewed, or a pre-merge gate. Run the full workflow limited to the change, using references/diff-review.md.

If it's ambiguous, ask one question: guidance pass or full audit (and which profile)?

Workflow (full audit)

  1. Scope: what's in, what's out, mode, and run profile
  2. Recon: write architecture.md and coverage.json before hunting
  3. Hunt: work the category checklist unit by unit (subagents for large codebases)
  4. Verify every finding: an independent refutation pass gives each candidate one verdict
  5. Coverage critic: look for unmapped surfaces and thin coverage
  6. Write and validate findings.json
  7. Render the report from the JSON

Read the full file on GitHub · 475 lines

Changes

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.

  1. today Changed · +110 lines · +55 tokens per session scan B → A 790b7cbcbbde
  2. 1mo ago First seen · 365 lines · 142 tokens per session scan B 0136edc20c0a

Subscribe to this mod's changes

owasp-audit is a cursor rule published in the GitHub repository briiirussell/cybersecurity-skills (435 stars, last pushed today), licensed MIT. It adds 197 tokens to every session and 12,289 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.