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 skills/atlasomnia/donna-starter/hermes-plugin-evaluationnpx skills add AtlasOmnia/donna-starter --skill hermes-plugin-evaluationgit clone --depth 1 https://github.com/AtlasOmnia/donna-starterWrote 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/donna-starter/hermes-plugin-evaluation)<a href="https://agentmods.dev/skills/atlasomnia/donna-starter/hermes-plugin-evaluation"><img src="https://agentmods.dev/badge/skills/atlasomnia/donna-starter/hermes-plugin-evaluation.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.00037 | $0.00743 |
| Opus 5 | $0.00018 | $0.00371 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
hermes-plugin-evaluation 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hermes-plugin-evaluation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Plugin Evaluation
Use this when the user asks about installing, trusting, pricing, or using a third-party Hermes Agent plugin or integration.
Goal
Give a practical go/no-go read before touching the live Hermes gateway. Separate:
- Plugin code cost/license — whether the repository itself is public/open-source/free to install.
- Service cost — required SaaS account, usage billing, phone/SMS/voice costs, model API costs, tunnels, hosted routing, or paid feature gates.
- Operational risk — what data leaves Hermes, whether the plugin opens public webhooks/tunnels, and whether it modifies gateway behavior.
Fast evaluation workflow
- Load authoritative Hermes context first when the task involves Hermes plugins:
- Load
hermes-agentif available. - Prefer official Hermes docs for CLI syntax and plugin lifecycle.
- Inspect the repository without installing it:
- README / docs
plugin.yamlpyproject.toml,package.json, lockfilesLICENSE,NOTICE, or equivalent- setup wizard files and
after-installnotes - tool definitions, platform adapter files, webhook/tunnel code
- Answer cost precisely:
- Say “plugin appears free/public” only for the repo/installable code.
- Do not infer the hosted service is free just because the plugin is public.
- Identify paid dependencies: phone numbers, SMS/MMS, voice minutes, hosted tunnels, OpenAI/Anthropic/etc. APIs, storage, or managed accounts.
- Check for a public pricing page, but treat absence as unknown, not free:
- If pricing is missing/404/gated, say “pricing not publicly obvious; confirm with vendor.”
- Report required credentials and data paths:
- Required env vars/API keys.
- Optional credentials that change cost or data flow.
- Whether inbound messages/calls pass through vendor infrastructure.
- Recommend a safe rollout:
- Test in a non-critical Hermes profile or disabled gateway first.
- Avoid putting it on the main gateway until pricing, credentials, and data flow are understood.
- Run plugin-specific
doctor/diagnostics before enabling public channels.
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.
- 6d ago First seen · 79 lines · 37 tokens per session scan A b7343b474243
hermes-plugin-evaluation is a skill published in the GitHub repository AtlasOmnia/donna-starter (104 stars, last pushed 7d ago), licensed MIT. It adds 37 tokens to every session and 743 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
npm-downloads-to-leads
Takes a list of npm package names (yours or competitors'), fetches 12 weeks of daily download data from the npm API, computes a breakout velocity score per package to identify hockey-stick growth, fetches maintainer profiles from the npm registry and GitHub API, and outputs a ranked lead brief for each breakout…
sdk-adoption-tracker
Given your SDK or library name, searches GitHub code search for public repos that import or require it, classifies each repo as company org, affiliated developer, solo developer, or tutorial noise, scores by adoption signal strength, detects new adopters by date, and outputs a ranked list of who is building on you…
domain-expired-opportunity-finder
Evaluates expired domain candidates against a target niche, scores them by topical relevance, historical activity level, and history cleanliness, then outputs a ranked shortlist with explainable reasoning and risk flags.
gh-issue-to-demand-signal
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's…
company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
linkedin-job-post-to-buyer-pain-map
Takes pasted LinkedIn job posts or hiring descriptions and converts them into a structured buyer pain map with inferred pains, capability gaps, buy-vs-build signal, account priority scores, and suggested outreach angles. Use when asked to analyze hiring posts, decode job descriptions for buyer intent, build a pain map…