The OWASP Cheat Sheet Series is a collection of concise guidance on application-security practices and specific security topics. It helps software builders design and maintain more secure applications. Its catalogue add-ons provide agents with ways to reference and apply this security guidance.
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.
git clone --depth 1 https://github.com/OWASP/CheatSheetSeriesWrote 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/agents/owasp/cheatsheetseries/cheatsheet-practicality-reviewer)<a href="https://agentmods.dev/agents/owasp/cheatsheetseries/cheatsheet-practicality-reviewer"><img src="https://agentmods.dev/badge/agents/owasp/cheatsheetseries/cheatsheet-practicality-reviewer/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/agents/owasp/cheatsheetseries/cheatsheet-practicality-reviewer"><img src="https://agentmods.dev/badge/agents/owasp/cheatsheetseries/cheatsheet-practicality-reviewer.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.00049 | $0.00712 |
| Opus 5.5 | $0.00020 | $0.00285 |
| Sonnet 5.5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
cheatsheet-practicality-reviewer 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 14d 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.
The source is not reproduced here
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 14d ago Changed 1f10fbba7870
- 1mo ago First seen · 45 lines · 49 tokens per session scan A dcc65f7d1879
cheatsheet-practicality-reviewer is an agent published in the GitHub repository OWASP/CheatSheetSeries (33,647 stars, last pushed yesterday), licensed CC-BY-SA-4.0. It adds 49 tokens to every session and 712 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
appsec-reviewer
Security reviewer for a single code change. Reads the diff, works out which security expectations it implicates, and grades the post-change code PASS/PARTIAL/FAIL/UNVERIFIABLE/NOTAPPLICABLE with file:line evidence and a code-aware fix → .requirements-verification.json. Grades against the active standard: the company…
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
ac-verifier
Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pr-commenter-batch
Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.