What is security-scan?

A command that checks a project for committed secrets and vulnerable Python dependencies. It uses Gitleaks for secret detection and Safety for dependency auditing when requirements files are present.

Use it as a pre-push security gate: install the required tools, scan the repository, check Python requirements files, and resolve findings before continuing.

It helps find exposed credentials and known dependency problems before code is pushed. It also records the scan results in the commit template's testing section.

security-scan — Command for Claude Code by ArogyaReddy

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/ArogyaReddy/alirezarezvani-claude-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/security-scan/github.svg)](https://agentmods.dev/commands/arogyareddy/alirezarezvani-claude-skills/security-scan)

Your own site

<a href="https://agentmods.dev/commands/arogyareddy/alirezarezvani-claude-skills/security-scan"><img src="https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/security-scan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/arogyareddy/alirezarezvani-claude-skills/security-scan"><img src="https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 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 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.00160
Opus 5.5	$0.00003	$0.00064
Sonnet 5.5	$0.00002	$0.00032
Haiku 4.5	$0.00001	$0.00016

Measured 2mo ago against content hash 24bedfc4a7f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-scan 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 2mo 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.

Origin

This is a copy

100% identical to security-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/security-scan.md · 23 lines

What it actually says

Ensure dependencies are installed:

pip install safety==3.2.4
brew install gitleaks  # or appropriate package manager

Scan for committed secrets:
```
gitleaks detect --verbose --redact
```
- Resolve any findings before continuing.

Audit Python dependencies (if requirements files exist):

for f in $(find . -name "requirements*.txt" 2>/dev/null); do
    safety check --full-report --file "$f"
done

Record results in the commit template's Testing section.
After a clean pass, proceed with commit and push workflow.

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.

2mo ago First seen · 23 lines · 8 tokens per session scan A 24bedfc4a7f1

Subscribe to this mod's changes

security-scan is a command published in the GitHub repository ArogyaReddy/alirezarezvani-claude-skills (39 stars, last pushed 7mo ago), licensed MIT. It adds 8 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. It is 100% identical to security-scan, differing in 0 lines, and is treated as a copy.