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 AtlasOmnia/hermes-custom-pack --skill skill-auditorgit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWrote 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/atlasomnia/hermes-custom-pack/skill-auditor)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/skill-auditor"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/skill-auditor.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.00064 | $0.03399 |
| Opus 5 | $0.00032 | $0.01699 |
| Sonnet 5 | $0.00013 | $0.00680 |
| Haiku 4.5 | $0.00006 | $0.00340 |
Grade A, and why
skill-auditor 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 4d 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.
This is a copy
100% identical to skill-auditor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Auditor — Quality Grading System (A–F)
Audit any Hermes skill file and assign a quality grade based on clarity, completeness, tool guidance, and shareability. Returns specific fix suggestions ranked by impact.
When to Use
- User asks you to review, audit, or grade a skill
- You're about to create a new skill and want to validate the draft
- A skill is behaving unreliably (agent skips it, calls wrong tools, misses steps)
- User shares a skill file or path for feedback
- You're preparing skills for sharing with others
Don't use for: general Hermes troubleshooting, model selection, config review — those have their own skills.
Grading Criteria
Each skill is scored across five dimensions. Points are deducted from 100. The final grade maps to a letter:
- Grade A (90–100) — Production-ready. Solid frontmatter, exact commands, real pitfalls, verification steps, consistent structure. Will fire reliably and execute correctly across model sizes.
- Grade B (80–89) — Minor gaps. Missing one dimension but still reliable.
- Grade C (70–79) — Functional but vague in places. Needs clarification on 1–2 key areas, especially with smaller models.
- Grade D (60–69) — Error-prone patterns detected. Incomplete steps or missing critical sections. Will fail silently on model switches.
- Grade F (<60) — Broken discovery or execution. Either the description is too vague to fire, or the steps are too incomplete to follow.
Dimension 1: Frontmatter & Description (max 25 points)
The description is your skill's only chance to be discovered. Hermes sees the one-line description from available_skills before deciding whether to load SKILL.md at all. If that description is vague, the skill never fires — nothing inside SKILL.md matters if this step fails.
Full marks (25): Valid YAML frontmatter with name and description fields. Description starts with "Use when..." and covers the trigger class (not a single task). Specific enough that Hermes can distinguish it from similar skills. ≤ 1024 chars.
- Example A:
Use when debugging Python: test failures, uncaught exceptions, silent bugs. Covers root cause analysis, not just error messages. - Example B:
Use when debugging code issues and test failures.(too broad — could overlap with other skills)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 270 lines · 64 tokens per session scan A 848759d9ad36
skill-auditor is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 24d ago), licensed MIT. It adds 64 tokens to every session and 3,399 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to skill-auditor, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-dreaming-agnostic
Memory-agnostic background consolidation — reviews sessions, scores candidates, promotes durable insights to the active memory backend (built-in MEMORY.md or Holographic). Three-phase (Light/Deep/Condensation/REM). Run via cron or manually.
config
Use when configuring obshare-cli credentials, checking saved settings, testing connectivity, clearing local config, or setting optional Obsidian bridge values used by the V0.2.0 direct-share stack.
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
upload
Use when uploading a Markdown note to Feishu, optionally applying public or copy/download permissions, or requesting JSON upload results for automation or the Obsidian plugin direct-share flow.
permission
Use when changing Feishu document visibility, copy permissions, or download permissions for an uploaded document token.
list
Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.