security-scan

security-scan is a command for Claude Code from boparaiamrit/skills-by-amrit. It costs 18 tokens per session (1,431 once invoked), scanned A, original, MIT.

A command for checking a software project for security issues in its code, dependencies, secrets, and configuration. It can scan a requested area or the whole project.

In plain words
What is it for?
Finding hardcoded passwords, tokens, API keys, private-key files, committed environment files, suspicious internal URLs or IP addresses, and dependency vulnerabilities.
Why use it?
It helps locate exposed credentials, private keys, risky internal addresses, and dependency problems before they become security incidents.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the skills-by-amrit plugin — 33 skills, 34 commands, 9 agents shipped together

Good fit Finding hardcoded passwords, tokens, API keys, private-key files, committed environment files, suspicious internal URLs or IP addresses, and dependency vulnerabilities.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/boparaiamrit/skills-by-amrit/security-scan
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/boparaiamrit/skills-by-amrit

Made for: Claude Code.

Or install skills-by-amrit, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 9 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 security-scan

README.md
[![agentmods](https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/security-scan/github.svg)](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/security-scan)
Your own site
<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/security-scan"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.

agentmods 80×15 button for security-scan

Your own site · 80×15
<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/security-scan"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,431 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.00018 $0.01431
Opus 5 $0.00009 $0.00715
Sonnet 5 $0.00004 $0.00286
Haiku 4.5 $0.00002 $0.00143

Measured 10d ago against content hash fdde921e743d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

commands/security-scan.md · 143 lines

How it starts

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

/security-scan — Security Analysis

Comprehensive security scan across code, dependencies, secrets, and configuration.

Instructions

Step 1: Determine Scope

From $ARGUMENTS:

  • If specific scope given: Scan that area only
  • If nothing: Full project scan

Step 2: Secret Detection

echo "=== SECRET SCAN ==="

# API keys, tokens, passwords
grep -rn "password\|secret\|api_key\|apikey\|token\|auth.*=\|bearer\|jwt" --include="*.ts" --include="*.js" --include="*.py" --include="*.env" --include="*.json" --include="*.yaml" --include="*.yml" . | grep -vi "node_modules\|.git\|dist\|test\|spec\|mock\|example\|placeholder\|process.env\|os.getenv\|os.environ" | head -30

# Private keys
find . -name "*.pem" -o -name "*.key" -o -name "*.p12" -o -name "id_rsa*" 2>/dev/null | grep -v node_modules

# .env files committed
git ls-files | grep -i "\.env" | grep -v ".example\|.sample\|.template"

# Hardcoded IPs/URLs that look like internal infrastructure
grep -rn "[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}" --include="*.ts" --include="*.js" . | grep -v node_modules | grep -v "127.0.0.1\|0.0.0.0\|localhost" | head -10

Step 3: Dependency Vulnerabilities

echo "=== DEPENDENCY AUDIT ==="
npm audit 2>&1
npm audit --production 2>&1

Step 4: Code Security Analysis

echo "=== CODE SECURITY ==="

# SQL injection potential (string concatenation in queries)
grep -rn "query\|execute.*\`\|execute.*+" --include="*.ts" --include="*.js" . | grep -v node_modules | grep -v "parameterized\|prepared" | head -20

# eval/exec usage
grep -rn "eval(\|exec(\|Function(\|setTimeout.*string\|setInterval.*string" --include="*.ts" --include="*.js" . | grep -v node_modules | head -10

# Unsanitized user input in HTML
grep -rn "innerHTML\|dangerouslySetInnerHTML\|document.write" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" . | grep -v node_modules | head -10

# Missing input validation
grep -rn "req.body\|req.params\|req.query" --include="*.ts" --include="*.js" . | grep -v node_modules | grep -v "validate\|sanitize\|zod\|joi\|yup" | head -20

# Insecure crypto
grep -rn "md5\|sha1\|Math.random" --include="*.ts" --include="*.js" . | grep -v node_modules | head -10

# CORS wildcards
grep -rn "Access-Control-Allow-Origin.*\*\|cors({.*origin.*true\|cors()" --include="*.ts" --include="*.js" . | grep -v node_modules | head -10

Read the full file on GitHub · 143 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. 10d ago First seen · 143 lines · 18 tokens per session scan A fdde921e743d

Subscribe to this mod's changes

security-scan is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,431 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.