cybersecurity

cybersecurity is a skill for Claude Code from AgriciDaniel/claude-cybersecurity. It costs 201 tokens per session (10,595 once invoked), scanned B, original, MIT.

A security review process for examining application code and its surrounding setup for common vulnerabilities, leaked secrets, unsafe dependencies, and attack paths. It uses established security categories such as OWASP and CWE to organize findings.

In plain words
What is it for?
Use it to audit source code, dependencies, deployment configuration, and infrastructure for application-security risks.
Why use it?
It helps identify security problems that may be missed in an ordinary code review, including issues spread across several parts of a system. It also focuses the review on how an attacker could use connected weaknesses.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Part of the claude-cybersecurity plugin — 1 skill shipped together

Good fit Use it to audit source code, dependencies, deployment configuration, and infrastructure for application-security risks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agricidaniel/claude-cybersecurity/cybersecurity
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.

Any agent
npx skills add AgriciDaniel/claude-cybersecurity --skill cybersecurity
Clone the repo
git clone --depth 1 https://github.com/AgriciDaniel/claude-cybersecurity

Made for: Claude Code.

Or install claude-cybersecurity, the plugin that ships this one along with the rest of its 1 skill.

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 cybersecurity

README.md
[![agentmods](https://agentmods.dev/badge/skills/agricidaniel/claude-cybersecurity/cybersecurity.svg)](https://agentmods.dev/skills/agricidaniel/claude-cybersecurity/cybersecurity)
Your own site
<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>
Per session 201 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,595 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00201 $0.10595
Opus 5 $0.00101 $0.05298
Sonnet 5 $0.00040 $0.02119
Haiku 4.5 $0.00020 $0.01060

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

Security

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.

skills/cybersecurity/SKILL.md · 987 lines

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

  1. GATHER — detect stack, enumerate entry points, identify trust boundaries
  2. ANALYZE — spawn 8 specialist agents in ONE parallel message
  3. RECOMMEND — aggregate weighted scores, chain attack paths, map compliance
  4. 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

Read the full file on GitHub · 987 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. 8d ago First seen · 987 lines · 201 tokens per session scan B f231f2aed6f0

Subscribe to this mod's changes

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.

Related

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.

Synvoya/codeinspectus · 55 tokens

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…

Synvoya/codeinspectus · 62 tokens

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…

CarbeneAI/Forge · 95 tokens

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…

CarbeneAI/Forge · 107 tokens

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…

Zyrexnn/Cybermes · 371 tokens

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…

Zyrexnn/Cybermes · 460 tokens