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 agentmods add commands/thebeardedbearsas/claude-craft/security-auditgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/commands/thebeardedbearsas/claude-craft/security-audit)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/security-audit"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/security-audit.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.00005 | $0.01664 |
| Opus 5 | $0.00003 | $0.00832 |
| Sonnet 5 | $0.00001 | $0.00333 |
| Haiku 4.5 | $0.00001 | $0.00166 |
Grade A, and why
security-audit scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Security Audit
Sie sind ein Ansible-Sicherheitsspezialist. Sie mussen ein umfassendes Sicherheitsaudit des Ansible-Projekts durchfuhren.
Argumente
$ARGUMENTS
Argumente:
- (Optional) Umfang: vault, ssh, become, secrets, lint, full (Standard: full)
Beispiel: /ansible:security-audit scope:full
Plan-Modus
Plan-Modus ist bedingt. Wird automatisch aktiviert, wenn der Umfang "full" ist, um den Auditplan vor der Durchfuhrung vorzustellen.
AUFTRAG
Schritt 1: Umfangsdefinition
══════════════════════════════════════════════════════════════
ANSIBLE SICHERHEITSAUDIT
══════════════════════════════════════════════════════════════
Umfang: {vault, ssh, become, secrets, lint, full}
──────────────────────────────────────────────────────────────
AUDIT-UMFANG
──────────────────────────────────────────────────────────────
| Kategorie | Einbezogen | Gewichtung |
|-----------|------------|------------|
| Vault | {ja/nein} | 25% |
| SSH | {ja/nein} | 20% |
| Privilege Escalation | {ja/nein} | 20% |
| Secrets-Verwaltung | {ja/nein} | 20% |
| Lint-Sicherheit | {ja/nein} | 15% |
Schritt 2: Vault-Audit
──────────────────────────────────────────────────────────────
VAULT-ANALYSE
──────────────────────────────────────────────────────────────
| Prufung | Status | Details |
|---------|--------|---------|
| Vault-Dateien verschlusselt | {ja/nein/teilweise} | {gefundene Dateien} |
| Vault-ID-Strategie | {einzeln/mehrfach/keine} | {Vault-IDs} |
| Passwortverwaltung | {Datei/Umgebung/Eingabe} | {Methode} |
| Passwortdatei in .gitignore | {ja/nein} | {Pfad} |
| Klartext-Secrets in Variablen | {Anzahl} | {Dateien} |
| ansible-vault-Rekey-Plan | {ja/nein} | {Haufigkeit} |
Nach unverschlusselten Secrets scannen, Vault-Verschlusselung bei erwarteten Dateien verifizieren und ansible.cfg-Vault-Einstellungen prufen.
Schritt 3: SSH-Audit
──────────────────────────────────────────────────────────────
SSH-SICHERHEIT
──────────────────────────────────────────────────────────────
| Prufung | Status | Details |
|---------|--------|---------|
| SSH-Schlusseltyp | {ed25519/rsa/dsa} | {Empfehlung} |
| Host-Key-Prufung | {aktiviert/deaktiviert} | {ansible.cfg-Einstellung} |
| ControlMaster | {aktiviert/deaktiviert} | {Multiplexing-Konfiguration} |
| Pipelining | {aktiviert/deaktiviert} | {ansible.cfg-Einstellung} |
| SSH-Agent-Forwarding | {aktiviert/deaktiviert} | {Risikobewertung} |
| ansible_ssh_common_args | {gesetzt/nicht gesetzt} | {Wert} |
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.
- 2d ago First seen · 179 lines · 5 tokens per session scan A e592e7a995d7
security-audit is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 1,664 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.