security-audit

security-audit is a skill for Claude Code from gabrieldabbah/genesis. It costs 111 tokens per session (1,840 once invoked), scanned A, original, MIT.

A structured review of a codebase or integration for security problems. It records each finding with its location, reason, severity, and a suggested fix.

In plain words
What is it for?
Use it before declaring work complete, after connecting an external service, before deployment, or when reviewing a codebase for security risks.
Why use it?
It turns vague concerns such as “is this safe?” into specific tasks that can be fixed or deliberately accepted before release.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the genesis plugin — 10 skills, 1 hook shipped together

Good fit Use it before declaring work complete, after connecting an external service, before…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gabrieldabbah/genesis/security-audit
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 gabrieldabbah/genesis --skill security-audit
Clone the repo
git clone --depth 1 https://github.com/gabrieldabbah/genesis

Made for: Claude Code.

Or install genesis, the plugin that ships this one along with the rest of its 10 skills, 1 hook.

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-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/gabrieldabbah/genesis/security-audit.svg)](https://agentmods.dev/skills/gabrieldabbah/genesis/security-audit)
Your own site
<a href="https://agentmods.dev/skills/gabrieldabbah/genesis/security-audit"><img src="https://agentmods.dev/badge/skills/gabrieldabbah/genesis/security-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 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.00111 $0.01840
Opus 5 $0.00056 $0.00920
Sonnet 5 $0.00022 $0.00368
Haiku 4.5 $0.00011 $0.00184

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

Security

Grade A, and why

security-audit 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 7d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

grep -rnE "innerHTML|dangerouslySetInnerHTML|eval\(|new Function|execSync|os\.system|pickle\.loads|yaml\.load\(" .
skills/security-audit/SKILL.md · 124 lines

How it starts

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

Security audit — score it, fix what is safe to fix, gate the rest

A finding without a location, a reason and a fix is not a finding. An audit that reports "nothing obvious" is not an audit — it is the absence of one.

1. Build the checklist

Start from the domains in §5. Add the per-integration items from each enabled service's registry entry (security: field). Tailor depth to what the thing is: deeper threat modelling for anything network-facing, data integrity for pipelines, the PCI surface for payments.

1a. Where a stronger scanner is installed, it does the hunting

Finding vulnerabilities and deciding what to do about them are different jobs, and this skill is better at the second than the first. A single read of a surface has no adversarial verification and no coverage accounting, so where a dedicated scanner is available, hand it the hunt and fold its output in here:

  • Anthropic's claude-security plugin, if installed. /claude-security opens its menu; scan a diff for a surface just built, or the whole codebase before a handoff. It partitions the tree, threat-models each component, and puts every candidate through a three-lens panel that defaults to false-positive — which is the part a single pass cannot reproduce. Its CLAUDE-SECURITY-RESULTS.jsonl is the evidence to fold in.
  • /security-review, if available.

Three reasons this stays a preference rather than a step: the plugin may not be installed on the machine running genesis, it cannot be invoked as a skill (only as its own command or agent), and it asks the operator to accept its cost before starting — which an unattended build cannot answer on their behalf. When none is available, or the run is unattended, do §2 onward directly and say in the report which path was taken.

What stays here either way, because no general scanner covers it: the per-integration checklist from the registry, dependency advisories, the domain ledger in §5, the fix-versus-gate line in §4, and turning findings into docs/TODO.md items that gate the build.

Read the full file on GitHub · 124 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. 7d ago First seen · 124 lines · 111 tokens per session scan A 8ea3e15fbfc2

Subscribe to this mod's changes

security-audit is a skill published in the GitHub repository gabrieldabbah/genesis (4 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 1,840 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

fleet

Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.

SethGammon/Citadel · 56 tokens

daemon

Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…

SethGammon/Citadel · 69 tokens

evolve

Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…

SethGammon/Citadel · 60 tokens

improve

Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.

SethGammon/Citadel · 48 tokens

setup

First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.

SethGammon/Citadel · 69 tokens

ascii-diagram

Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

SethGammon/Citadel · 43 tokens