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 skills add amanning3390/hermeshub --skill security-auditorgit clone --depth 1 https://github.com/amanning3390/hermeshubWrote 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/skills/amanning3390/hermeshub/security-auditor)<a href="https://agentmods.dev/skills/amanning3390/hermeshub/security-auditor"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/security-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amanning3390/hermeshub/security-auditor"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/security-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00714 |
| Opus 5.5 | $0.00015 | $0.00286 |
| Sonnet 5.5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 1mo 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) 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
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.
- 1mo ago First seen · 98 lines · 37 tokens per session scan A 5e04b084d8c1
security-auditor is a skill published in the GitHub repository amanning3390/hermeshub (48 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 714 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…