LegendaryTeam_For_Claude: Command for Claude Code

.claude/commands/security-scan.md

security-scan is a command for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 0 tokens per session (5,004 once invoked), scanned A, original, MIT.

A command that scans a project for several kinds of security problems, including vulnerable dependencies, unsafe code, exposed secrets, container issues, license concerns, and missing web security headers.

In plain words
What is it for?
Use it to scan all supported areas or focus on dependencies, secrets, severity levels, or JSON output for continuous-integration systems.
Why use it?
It brings different security checks into one project scan and reports the findings for review.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything LegendaryTeam_For_Claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/security-scan.md
Clone the repo
git clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_Claude

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.

agentmods badge for security-scan

README.md
[![agentmods](https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/security-scan/github.svg)](https://agentmods.dev/commands/regardv/legendaryteam_for_claude/security-scan)
Your own site
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/security-scan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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/regardv/legendaryteam_for_claude/security-scan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 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.00000 $0.05004
Opus 5 $0.00000 $0.02502
Sonnet 5 $0.00000 $0.01001
Haiku 4.5 $0.00000 $0.00500

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

Security

Grade A, and why

security-scan scanned grade A with 2 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.

Asks for rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

# or: wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

# or: wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -
.claude/commands/security-scan.md · 796 lines

How it starts

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

Security Scan

Run comprehensive security vulnerability scans and report findings to @chief.


What This Command Does

Automatically runs security scans across multiple layers:

  1. Dependency vulnerabilities - Known CVEs in packages
  2. Code vulnerabilities - Static analysis for security issues
  3. Secrets detection - Exposed API keys, passwords, tokens
  4. Container security - Docker image vulnerabilities (if applicable)
  5. License compliance - Check for restrictive licenses
  6. Security headers - HTTP security header validation (if web app)

Then reports all findings to @SecurityAgent and @chief for review.


Usage

/security-scan

Optional flags:

/security-scan --fix              # Auto-fix vulnerabilities where safe
/security-scan --dependencies-only # Only scan packages
/security-scan --secrets-only      # Only check for exposed secrets
/security-scan --severity=high     # Only show high/critical issues
/security-scan --json              # Output JSON for CI/CD

Implementation

This command auto-detects your project and runs appropriate security tools.

Auto-Detection & Tool Selection

Node.js/JavaScript Projects:

if [ -f "package.json" ]; then
  # npm audit (built-in)
  npm audit --json > npm-audit.json

  # Snyk (if installed)
  if command -v snyk &> /dev/null; then
    snyk test --json > snyk-results.json
  fi

  # retire.js for outdated libraries
  if command -v retire &> /dev/null; then
    retire --json > retire-results.json
  fi
fi

Python Projects:

if [ -f "requirements.txt" ] || [ -f "Pipfile" ] || [ -f "pyproject.toml" ]; then
  # safety for known vulnerabilities
  if command -v safety &> /dev/null; then
    safety check --json > safety-results.json
  fi

  # bandit for code security issues
  if command -v bandit &> /dev/null; then
    bandit -r . -f json -o bandit-results.json
  fi

  # pip-audit
  if command -v pip-audit &> /dev/null; then
    pip-audit --format json > pip-audit.json
  fi
fi

Read the full file on GitHub · 796 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. 9d ago First seen · 796 lines · 0 tokens per session scan A 18defe8da772

Subscribe to this mod's changes

security-scan is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,004 tokens. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.