agentleFS
amanning3390amanning3390/hermeshub/skills/security-auditor/SKILL.md

security-auditor

Skill48 starsChanged 5 months agoMITView on GitHub

Scan code for vulnerabilities, secret leaks, dependency issues, and configuration problems. Use when the user wants a security audit, vulnerability scan, or code security review.

  • Reads credentials

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use proofreader, refactoring-guide and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xcrrrSkill

    proofreader

    Use this skill when reviewing written content for grammar, spelling, punctuation, style consistency, and tone—before publishing, submitting, or sending. Trigger phrases: 'proofread this', 'check my writing', 'review this for errors', 'edit this email/report/essay'. Do NOT use when structural rewrites or content changes are needed—proofreading fixes surface errors, not substantive problems.

    Also in 3 projects that use this

  • peopleforresterSkill

    refactoring-guide

    Safe refactoring patterns and techniques. Use when the user wants to improve code structure, reduce duplication, or make code more maintainable without changing behavior. Emphasizes incremental changes with test coverage.

    Also in 3 projects that use this

  • zwjbendnSkill

    habit-builder

    Designs and manages healthy habits for sustainable weight loss through lifestyle change. Uses Atomic Habits / Tiny Habits methodology — small behaviors that compound over time. Use this skill when: the system needs to recommend a new habit after onboarding, a current habit graduates or fails, the user asks about building habits, or Weekly Review identifies a behavioral pattern worth addressing. Also use when evaluating habit progress, deciding when a habit has "graduated," or handling a restart after the user falls off. This skill does not send its own reminders — habit check-ins are woven into meal conversations managed by Notification Composer. This skill owns the check-in logic (when, how often, tone); Notification Composer provides the conversation vehicle.

    Also in 3 projects that use this

  • juanlurgSkill

    sql-optimizer

    Analyzes SQL queries and generates an optimization report notebook with explanations, identified issues, and rewritten queries. Use when the user wants to optimize, explain, improve, or debug a SQL query, or mentions query performance, slow queries, or SQL optimization.

    Also in 3 projects that use this

  • belokonmSkill

    data-scientist

    Expert in statistical analysis, predictive modeling, machine learning, and data storytelling to drive business insights.

    Also in 3 projects that use this

  • glinckerSkill

    qa-engineer

    QA specialist agent for test planning, execution, and regression analysis

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before deploying to production

    line 23
  2. Distinctive:

    When reviewing third-party code or skills

    line 24
  3. Distinctive:

    Search for accidentally committed secrets:

    line 29
  4. Distinctive:

    Check for data exfiltration patterns (curl to external URLs)

    line 63
  5. Distinctive:

    Look for prompt injection attempts

    line 64
  6. Distinctive:

    Verify no destructive commands without confirmation

    line 65
  7. Distinctive:

    Check environment variable access patterns

    line 66
  8. Distinctive:

    Don't expose actual secret values in reports

    line 90
  9. Distinctive:

    All critical/high findings have remediation steps

    line 95
  10. Distinctive:

    No actual secrets appear in the audit report itself

    line 96

“Common” is measured: kept by at least 6 in 10 of the 47 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Verification

  • All critical/high findings have remediation steps
  • No actual secrets appear in the audit report itself
  • Report includes scan methodology and tool versions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.