security-auditor

security-auditor is a skill for Claude Code, Codex from amanning3390/hermeshub. It costs 37 tokens per session (714 once invoked), scanned A, original, MIT.

A code-review workflow that checks software for security weaknesses, leaked secrets, unsafe dependencies, and configuration mistakes. Dependencies are third-party packages that the code relies on.

In plain words
What is it for?
Use it for security audits, secret scans, dependency checks, reviews of third-party code or coding-agent add-ons, and checks based on the OWASP Top 10 security risks.
Why use it?
It helps find problems that could expose credentials, allow attacks, or make a deployment unsafe before the software reaches production.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for security audits, secret scans, dependency checks, reviews of third-party code or coding-agent add-ons, and checks based on the OWASP Top 10 security risks.

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

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/amanning3390/hermeshub/security-auditor.svg)](https://agentmods.dev/skills/amanning3390/hermeshub/security-auditor)
Your own site
<a href="https://agentmods.dev/skills/amanning3390/hermeshub/security-auditor"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/security-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 714 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.00037 $0.00714
Opus 5 $0.00018 $0.00357
Sonnet 5 $0.00007 $0.00143
Haiku 4.5 $0.00004 $0.00071

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

Security

Grade A, and why

security-auditor 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Check for data exfiltration patterns (curl to external URLs)
skills/security-auditor/SKILL.md · 98 lines

How it starts

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

Security Auditor

Comprehensive security scanning and audit reporting.

When to Use

  • User asks for a security audit or vulnerability scan
  • User wants to check code for secret leaks
  • User needs dependency vulnerability checking
  • Before deploying to production
  • When reviewing third-party code or skills

Procedure

1. Secret Scanning

Search for accidentally committed secrets:

# Common patterns to search
grep -rn "API_KEY\|SECRET\|PASSWORD\|TOKEN\|PRIVATE_KEY" --include="*.{py,js,ts,env,yml,yaml,json}" .
grep -rn "sk-[a-zA-Z0-9]\{20,\}" . # OpenAI keys
grep -rn "ghp_[a-zA-Z0-9]\{36\}" . # GitHub PATs
grep -rn "AKIA[0-9A-Z]\{16\}" . # AWS Access Keys

2. Dependency Audit

# Node.js
npm audit --json
# Python
pip-audit
# Docker
docker scout cves image:tag

3. Code Analysis (OWASP Top 10)

Check for:

  • A01: Broken Access Control
  • A02: Cryptographic Failures
  • A03: Injection (SQL, Command, XSS)
  • A04: Insecure Design
  • A05: Security Misconfiguration
  • A06: Vulnerable Components
  • A07: Auth Failures
  • A08: Software/Data Integrity Failures
  • A09: Logging/Monitoring Failures
  • A10: SSRF

4. Hermes Skill Security Scan

For reviewing skills before installation:

  • Check for data exfiltration patterns (curl to external URLs)
  • Look for prompt injection attempts
  • Verify no destructive commands without confirmation
  • Check environment variable access patterns
  • Scan for obfuscated code or encoded payloads

Report Format

# Security Audit Report
**Target:** [project/skill name]
**Date:** [date]
**Risk Level:** Critical/High/Medium/Low

## Findings
| # | Severity | Category | Description | Location |
|---|----------|----------|-------------|----------|
| 1 | Critical | Secrets  | Exposed API key | config.py:42 |

## Recommendations
1. [Prioritized remediation steps]

## Summary
- Critical: X | High: X | Medium: X | Low: X

Pitfalls

  • False positives are common — verify each finding
  • Don't expose actual secret values in reports
  • Some test fixtures intentionally contain fake credentials
  • Audit transitive dependencies, not just direct ones

Read the full file on GitHub · 98 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 · 98 lines · 37 tokens per session scan A 5e04b084d8c1

Subscribe to this mod's changes

security-auditor is a skill published in the GitHub repository amanning3390/hermeshub (35 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 714 once invoked, about $0.0002 per session on Opus 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-30.