Security Review

Security Review is a skill for Claude Code, Codex from theashishmaurya/pr-review-agent. It costs 11 tokens per session (387 once invoked), scanned A, original, MIT.

A focused review checklist for finding security weaknesses in an application and checking common protection practices.

In plain words
What is it for?
Use it to review authentication, authorization, passwords, uploads, queries, browser security, data protection, and other common application-security areas.
Why use it?
It helps uncover issues such as missing access checks, unsafe input handling, exposed secrets, injection risks, and insecure dependencies before they cause harm.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review authentication, authorization, passwords, uploads, queries, browser security, data protection, and other common application-security areas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/theashishmaurya/pr-review-agent/security
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.

Any agent
npx skills add theashishmaurya/pr-review-agent --skill security
Clone the repo
git clone --depth 1 https://github.com/theashishmaurya/pr-review-agent

Made for: Claude Code, Codex.

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 Security Review

README.md
[![agentmods](https://agentmods.dev/badge/skills/theashishmaurya/pr-review-agent/security/github.svg)](https://agentmods.dev/skills/theashishmaurya/pr-review-agent/security)
Your own site
<a href="https://agentmods.dev/skills/theashishmaurya/pr-review-agent/security"><img src="https://agentmods.dev/badge/skills/theashishmaurya/pr-review-agent/security/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 Security Review

Your own site · 80×15
<a href="https://agentmods.dev/skills/theashishmaurya/pr-review-agent/security"><img src="https://agentmods.dev/badge/skills/theashishmaurya/pr-review-agent/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00011 $0.00387
Opus 5 $0.00005 $0.00193
Sonnet 5 $0.00002 $0.00077
Haiku 4.5 $0.00001 $0.00039

Measured 9d ago against content hash 88ca63a1db76, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

skills/security/SKILL.md · 67 lines

What it actually says

Security Review Skill

Focus exclusively on security vulnerabilities and best practices.

Authentication & Authorization

  • Authentication checks on all protected routes
  • Authorization checks before sensitive operations
  • Session management secure
  • Password/credential handling secure

Input Validation

  • All user input validated and sanitized
  • No direct string interpolation in queries
  • File uploads validated (type, size, content)
  • URL parameters sanitized

Common Vulnerabilities

  • SQL Injection: Use parameterized queries
  • XSS: Escape output, use CSP headers
  • CSRF: Include CSRF tokens
  • SSRF: Whitelist allowed URLs
  • Path Traversal: Validate file paths
  • Command Injection: Avoid shell commands with user input

Data Protection

  • Sensitive data encrypted at rest
  • HTTPS for data in transit
  • No secrets in code or logs
  • PII handled per regulations

Dependencies

  • No known vulnerable dependencies
  • Lock files present and valid

Security Headers

For web applications:

  • Content-Security-Policy
  • X-Frame-Options
  • X-Content-Type-Options
  • Strict-Transport-Security

Severity Guide

🚨 Critical: Active vulnerability, immediate fix required ⚠️ Warning: Security concern, should fix soon 💡 Info: Best practice recommendation

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. 9d ago First seen · 67 lines · 11 tokens per session scan A 88ca63a1db76

Subscribe to this mod's changes

Security Review is a skill published in the GitHub repository theashishmaurya/pr-review-agent (2 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 387 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens