Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matteocervelli/llms/main/.claude/skills/security-verify/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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.
[](https://agentmods.dev/skills/matteocervelli/llms/security-verify)<a href="https://agentmods.dev/skills/matteocervelli/llms/security-verify"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/security-verify.svg" alt="Measured on agentmods" height="20"></a>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.00074 | $0.03237 |
| Opus 5 | $0.00037 | $0.01618 |
| Sonnet 5 | $0.00015 | $0.00647 |
| Haiku 4.5 | $0.00007 | $0.00324 |
Grade A, and why
security-verify scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` (always available, zero extra deps) How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Verify — Verification Workflows
Run security verification checks: pattern scanning, OWASP compliance, and vulnerability assessment.
Usage
/security-verify # Default: run scan mode
/security-verify scan [path] # Pattern-based security scanning (SAST)
/security-verify dast <url> # Dynamic testing against running app (DAST)
/security-verify owasp # OWASP Top 10 compliance check
/security-verify assess # Vulnerability CVSS scoring + remediation
/security-verify audit # Adversarial logic-level code review (CWE + CVSS + exploit)
/security-verify full # scan + audit combined (use for /health or manual deep check)
Mode: scan
Run pattern-based security scanning against the codebase.
What It Checks
- Secret Detection — Hardcoded credentials, API keys, private keys
- SQL Injection — String interpolation in queries, raw SQL
- XSS — Disabled auto-escaping, innerHTML, unsafe template filters
- Command Injection — Unsafe subprocess/exec patterns
- Insecure Deserialization — Unsafe deserializers
- Weak Cryptography — MD5, SHA1, weak random for security use
- Multi-Tenant Violations — tenant_id from request, missing tenant filters
- Cookie Issues — Missing __Host- prefix, missing samesite
Scan Execution
Run the scanner script against target path:
# Full scan — manual usage, scans entire directory
bash "$HOME/.claude/skills/security-verify/lib/scanner-runner.sh" "${TARGET_PATH:-.}"
# Staged-only scan — pre-commit context, scans only git-staged files
bash "$HOME/.claude/skills/security-verify/lib/scanner-runner.sh" --staged
Use --staged when invoked from /pre-commit to limit scope to the current commit's changes.
Full-path scanning is for standalone audits.
Review findings, assess severity, and provide fix recommendations.
Dependency Audit
After pattern scan, check for known CVEs:
# Use filtered requirements file to audit only public packages.
if command -v uv &>/dev/null && ([ -f uv.lock ] || [ -f pyproject.toml ]); then
if uv export --no-hashes --frozen > /tmp/raw-reqs.txt 2>/dev/null; then :; else
uv run pip freeze > /tmp/raw-reqs.txt 2>/dev/null || true
fi
uv run --with pip-audit pip-audit -r /tmp/pip-audit-reqs.txt 2>/dev/null || true
elif command -v pip-audit &>/dev/null; then
pip-audit --local 2>/dev/null || true
else
echo "pip-audit not installed"
fi
npm audit --production 2>/dev/null || echo "No package.json"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 277 lines · 74 tokens per session scan A bdfbb8cf95fc
security-verify is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 3,237 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…