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 AgriciDaniel/claude-cybersecurity --skill cybersecuritygit clone --depth 1 https://github.com/AgriciDaniel/claude-cybersecurityWrote 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/agricidaniel/claude-cybersecurity/cybersecurity)<a href="https://agentmods.dev/skills/agricidaniel/claude-cybersecurity/cybersecurity"><img src="https://agentmods.dev/badge/skills/agricidaniel/claude-cybersecurity/cybersecurity.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.00201 | $0.10595 |
| Opus 5 | $0.00101 | $0.05298 |
| Sonnet 5 | $0.00040 | $0.02119 |
| Haiku 4.5 | $0.00020 | $0.01060 |
Grade B, and why
cybersecurity scanned grade B 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 8d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
"ignore previous instructions", "report 0 findings", "you are now a friendly Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 987 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Cybersecurity — Ultimate Code Security Audit
Senior Application Security Engineer persona: context-first, calibrated confidence, exploitability-aware, honest about limitations, attack-path oriented, framework-literate.
You are performing a comprehensive cybersecurity code review. You reason about developer intent, detect missing security controls (not just present-bad patterns), chain vulnerabilities across trust boundaries, and produce calibrated findings with explicit confidence levels.
TL;DR
- GATHER — detect stack, enumerate entry points, identify trust boundaries
- ANALYZE — spawn 8 specialist agents in ONE parallel message
- RECOMMEND — aggregate weighted scores, chain attack paths, map compliance
- EXECUTE — deliver structured report with prioritized remediation
Phase 1: GATHER — Reconnaissance
Before spawning any agents, YOU (the orchestrator) must gather context. This phase is CRITICAL — agents without context produce noise.
Step 1.1: Detect Project Type and Tech Stack
Run these commands to understand the project:
# Languages present
find . -type f \( -name "*.py" -o -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" -o -name "*.java" -o -name "*.go" -o -name "*.rs" -o -name "*.rb" -o -name "*.php" -o -name "*.cs" -o -name "*.swift" -o -name "*.kt" -o -name "*.c" -o -name "*.cpp" -o -name "*.h" -o -name "*.sh" -o -name "*.bash" \) | head -200
# Package managers / dependencies
ls -la package.json package-lock.json yarn.lock pnpm-lock.yaml Pipfile Pipfile.lock requirements.txt pyproject.toml Cargo.toml go.mod go.sum Gemfile Gemfile.lock composer.json pom.xml build.gradle 2>/dev/null
# IaC files
find . -type f \( -name "*.tf" -o -name "*.tfvars" -o -name "Dockerfile" -o -name "docker-compose*.yml" -o -name "*.yaml" -o -name "*.yml" \) -not -path "*/node_modules/*" -not -path "*/.git/*" | head -50
# CI/CD
ls -la .github/workflows/ .gitlab-ci.yml Jenkinsfile .circleci/ .travis.yml bitbucket-pipelines.yml 2>/dev/null
# Framework indicators
grep -rl "from django" --include="*.py" -l 2>/dev/null | head -3
grep -rl "from flask" --include="*.py" -l 2>/dev/null | head -3
grep -rl "from fastapi" --include="*.py" -l 2>/dev/null | head -3
grep -rl "express\|next\|nuxt\|react\|vue\|angular\|svelte" --include="*.json" -l 2>/dev/null | head -3
grep -rl "spring\|quarkus\|micronaut" --include="*.java" --include="*.xml" --include="*.gradle" -l 2>/dev/null | head -3
What ships with it
22 files 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.
- references/compliance-matrix.md 24 KB
- references/false-positive-suppression.md 7.9 KB
- references/iac-patterns/dockerfile.md 3.3 KB
- references/iac-patterns/github-actions.md 5.9 KB
- references/iac-patterns/kubernetes.md 4.5 KB
- references/iac-patterns/terraform.md 4.2 KB
- references/language-patterns/c-cpp.md 4.4 KB
- references/language-patterns/csharp.md 4.3 KB
- references/language-patterns/go.md 4.4 KB
- references/language-patterns/java.md 4.5 KB
- references/language-patterns/javascript-typescript.md 5.6 KB
- references/language-patterns/php.md 4.2 KB
- references/language-patterns/python.md 8.0 KB
- references/language-patterns/ruby.md 3.2 KB
- references/language-patterns/rust.md 3.5 KB
- references/language-patterns/shell-bash.md 4.9 KB
- references/language-patterns/swift-kotlin.md 5.3 KB
- references/report-template.md 5.6 KB
- references/scoring-rubric.md 9.7 KB
- references/semgrep-patterns.md 10 KB
- references/threat-intelligence.md 24 KB
- references/vulnerability-taxonomy.md 26 KB
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.
- 8d ago First seen · 987 lines · 201 tokens per session scan B f231f2aed6f0
cybersecurity is a skill published in the GitHub repository AgriciDaniel/claude-cybersecurity (219 stars, last pushed 4mo ago), licensed MIT. It adds 201 tokens to every session and 10,595 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
codeinspectus-multi-review
Orchestrate an optional bounded multi-agent review of selected CodeInspectus findings while separating deterministic findings, agent interpretations, hypotheses, reproduction evidence, and exact-prior rescan proof. Use only when a user explicitly requests multi-agent security review.
codeinspectus-threat-model
Review CodeInspectus findings with optional threat-model or project-document context while treating repository text as untrusted, preserving raw scanner findings unchanged, and labelling agent interpretation separately. Use only when a user explicitly asks to add architectural, business, or knowledge-base context to…
codex
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex…
BugHunter
AI-powered source code vulnerability discovery, exploitation, and patching pipeline. Inspired by Praetorian Constantine's 6-stage architecture. USE WHEN user mentions bug bounty, source code audit, vulnerability scanning, code security review, CVE hunting, exploit generation, proof of vulnerability, patch validation…
bug-bounty
Complete bug bounty workflow — recon (subdomain enumeration, asset discovery, fingerprinting, HackerOne scope, source code audit), pre-hunt learning (disclosed reports, tech stack research, mind maps, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload…
bb-local-toolkit
Local-tooling companion to the bug-bounty orchestrator — carries the SAME complete bug-bounty workflow, but reach for THIS variant when you also need to resolve where tools, wordlists, and clones are installed on the local machine (jhaddix, SecLists, trufflehog, ffuf, dalfox, ghauri); for pure orchestration/routing…