check-security

check-security is a command for Claude Code from luongnv89/claude-howto. It costs 5 tokens per session (160 once invoked), scanned A, original, MIT.

A command for reviewing code changes specifically for security problems, such as weak login controls, exposed data, injection vulnerabilities, and unsafe cryptography.

In plain words
What is it for?
Use it to inspect changed code for authentication and authorization issues, data exposure, injection attacks, cryptographic weaknesses, and sensitive information in logs.
Why use it?
It focuses attention on risks that ordinary code review may miss and that can lead to unauthorized access or data leaks.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the pr-review plugin — 3 commands, 3 agents shipped together

Good fit Use it to inspect changed code for authentication and authorization issues, data exposure, injection attacks, cryptographic weaknesses, and sensitive information in logs.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/luongnv89/claude-howto/check-security
About the project

luongnv89/claude-howto is a visual, example-based guide to Claude Code, a coding tool that supports agents, hooks, skills, slash commands, and MCP servers. Developers use it to learn Claude Code through practical workflows and copyable templates, including the commands, agents, skills, plugins, and instructions catalogued here.

luongnv89/claude-howto · 42,095 stars · on GitHub · luongnv.com

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/luongnv89/claude-howto

Made for: Claude Code.

Or install pr-review, the plugin that ships this one along with the rest of its 3 commands, 3 agents.

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 check-security

README.md
[![agentmods](https://agentmods.dev/badge/commands/luongnv89/claude-howto/check-security/github.svg)](https://agentmods.dev/commands/luongnv89/claude-howto/check-security)
Your own site
<a href="https://agentmods.dev/commands/luongnv89/claude-howto/check-security"><img src="https://agentmods.dev/badge/commands/luongnv89/claude-howto/check-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 check-security

Your own site · 80×15
<a href="https://agentmods.dev/commands/luongnv89/claude-howto/check-security"><img src="https://agentmods.dev/badge/commands/luongnv89/claude-howto/check-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 160 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.00005 $0.00160
Opus 5.5 $0.00002 $0.00064
Sonnet 5.5 $0.00001 $0.00032
Haiku 4.5 $0.00001 $0.00016

Measured 5d ago against content hash 97f6c91079de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check-security 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 5d 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.

07-plugins/pr-review/commands/check-security.md · 23 lines

What it actually says

Security Check

Perform focused security analysis on code changes:

  1. Authentication/authorization checks
  2. Data exposure risks
  3. Injection vulnerabilities
  4. Cryptographic weaknesses
  5. Sensitive data in logs

Last Updated: October 15, 2026 Claude Code Version: 2.1.300 Sources:

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. 5d ago Changed · -3 tokens per session 97f6c91079de
  2. 1mo ago First seen · 23 lines · 8 tokens per session scan A db10a5131eca

Subscribe to this mod's changes

check-security is a command published in the GitHub repository luongnv89/claude-howto (42,095 stars, last pushed today), licensed MIT. It adds 5 tokens to every session and 160 once invoked, about $0.0000 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.