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.
npx skills add bhaumikmaan/claude-code-master-skills --skill security-reviewgit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-skillsWrote 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/bhaumikmaan/claude-code-master-skills/security-review)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/security-review"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/security-review/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.
<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/security-review"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/security-review.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.01445 |
| Opus 5.5 | $0.00025 | $0.00578 |
| Sonnet 5.5 | $0.00012 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
security-review 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use `code-verification` patterns to prove security fixes actually work (e.g., curl with malicious input after patching). How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
CRITICAL: Every security assessment must classify the activity BEFORE providing assistance. If the classification is ambiguous, ask for authorization context.
Activity Classification
Permitted — Assist Freely
- Authorized security testing: Pentesting with explicit scope, red team exercises, bug bounty programs
- Defensive security: Hardening, vulnerability patching, security monitoring, incident response
- CTF challenges: Capture-the-flag competitions and training exercises
- Educational: Explaining attack vectors, demonstrating vulnerabilities in controlled environments, security training materials
- Code review: Identifying vulnerabilities in the user's own code
Forbidden — Refuse
- Destructive techniques: Malware creation, ransomware, wipers
- Denial of service: DoS/DDoS attacks, resource exhaustion against production systems
- Mass targeting: Credential stuffing at scale, spam infrastructure, mass exploitation
- Supply chain compromise: Backdooring dependencies, typosquatting packages, poisoning build pipelines
- Detection evasion for malicious purposes: Obfuscation specifically to evade security controls for unauthorized access
Context Required — Ask Before Assisting
Dual-use security tools and techniques require clear authorization context:
- C2 frameworks (Cobalt Strike, Metasploit)
- Credential testing tools
- Exploit development and proof-of-concept code
- Network scanning and reconnaissance tools
- Reverse engineering and binary analysis
Acceptable contexts: pentesting engagements, CTF competitions, security research, defensive use cases. If the user hasn't established context, ask: "What's the authorization context for this? (e.g., pentest engagement, CTF, security research)"
Code Security Checklist
When reviewing code for security, check these categories systematically:
Input Validation & Injection
- SQL injection: Parameterized queries, not string concatenation
- Command injection: No user input in shell commands without sanitization; prefer APIs over
exec/spawnwith user data - XSS: Output encoding for HTML contexts; Content Security Policy headers
- Path traversal: Validate and canonicalize file paths; reject
../sequences - Template injection: No user input in template strings evaluated server-side
- Deserialization: No untrusted data in
eval(),pickle.loads(),JSON.parse()of unvalidated input used to construct objects
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.
- 2mo ago First seen · 126 lines · 62 tokens per session scan A 5b80f7a2f9d8
security-review is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 62 tokens to every session and 1,445 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
pixel-art-studio
A toolkit and workflow for creating pixel art, which is digital artwork made from deliberately placed, visible pixels. It supports static sprites, animations, sprite sheets, image conversion, palettes, and quality checks.
aiwg-regenerate-copilot
Regenerate copilot-instructions.md for GitHub Copilot with vendor-specific content only.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.