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 moonlight-lupin/agent-skills --skill hermes-onboardinggit clone --depth 1 https://github.com/moonlight-lupin/agent-skillsWrote 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/moonlight-lupin/agent-skills/hermes-onboarding)<a href="https://agentmods.dev/skills/moonlight-lupin/agent-skills/hermes-onboarding"><img src="https://agentmods.dev/badge/skills/moonlight-lupin/agent-skills/hermes-onboarding/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/moonlight-lupin/agent-skills/hermes-onboarding"><img src="https://agentmods.dev/badge/skills/moonlight-lupin/agent-skills/hermes-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 57 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Rogue Agent · line 80 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00023 | $0.07400 |
| Opus 5.5 | $0.00009 | $0.02960 |
| Sonnet 5.5 | $0.00005 | $0.01480 |
| Haiku 4.5 | $0.00002 | $0.00740 |
Grade B, and why
hermes-onboarding scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. **Gateway platform(s)** — Telegram, Discord, WhatsApp, Slack, Signal. Collect bot tokens or pairing info. Tokens are stored in `~/.hermes/.env` (chmod 600). Do not paste tokens into chat transcripts. How it starts
The opening of the file, as written. The whole thing — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Onboarding
Configure a fresh Hermes Agent from a working base chat to a production-ready deployment.
Precondition: Hermes is installed and the main model + provider are configured. Verify with hermes doctor. If the agent cannot complete a normal chat, stop here and fix the provider first.
Leading word: onboard — configure every layer before declaring the setup complete.
When to Use
- A customer has a fresh Hermes install with a working base chat and needs full configuration
- An operator is setting up Hermes on a new VPS or machine for production use
- A customer wants to go from "it works" to "it is secured, memory-enabled, always-on, and maintained"
Do not use if the main model is not yet configured. Fix the provider first.
Step 0 — Load references
Load references/setup-details.md. It holds config snippets, systemd templates, DonSeTch MCP config, skill guardrail principles, and verbosity examples.
Done: references file loaded into context.
Step 1 — Detect environment
Run the detection block from references/setup-details.md § Detection. Collect:
| Item | How |
|---|---|
| OS | uname -a |
| systemd | systemctl --version |
| Docker | docker --version |
| root vs user | whoami |
| container vs bare metal | head -5 /proc/1/cgroup |
| Hermes path | which hermes |
| Hermes version | hermes --version |
| Main model vision | Check model capabilities via provider docs or test with vision_analyze |
Done: all 8 items detected and recorded. No user input required.
Step 2 — Ask up-front questions
Ask the customer 3 questions in one batch:
- Customer name — used for profile name and soul.md identity
- Timezone — IANA timezone (e.g. Asia/Singapore, America/New_York)
- Gateway platform(s) — Telegram, Discord, WhatsApp, Slack, Signal. Collect bot tokens or pairing info. Tokens are stored in
~/.hermes/.env(chmod 600). Do not paste tokens into chat transcripts.
If Step 1 detected the main model lacks vision, add a 4th question:
What ships with it
4 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.
- 1mo ago Changed · +105 lines 24944181be7b
- 1mo ago Changed · +23 lines ea6634801dfe
- 1mo ago First seen · 473 lines · 23 tokens per session scan B f897221d8a6a
hermes-onboarding is a skill published in the GitHub repository moonlight-lupin/agent-skills (112 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 7,400 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
telnyx-storage-curl
Manage cloud storage buckets and objects using the S3-compatible Telnyx Storage API. This skill provides REST API (curl) examples.
domain-monitoring
AI-powered domain and SSL certificate monitoring skill. Designs domain health checks, SSL expiry alerts, DNS anomaly detection, and security rating assessments for e-commerce websites.
public-status-page
AI-powered public status page design skill for e-commerce businesses. Creates status page architecture, incident communication templates, subscriber notification systems, and uptime reporting frameworks.
huawei-cloud-agentarts-otel-ingestion
OpenTelemetry ingestion skill for Huawei Cloud AgentArts observability platform. Provides OTel telemetry data (trace/metrics/logs) ingestion into AgentArts agent-ops, AI Agent observation with genai semantic conventions, auto-configuration for Java/Python/Node.js/Go applications, and ingestion diagnostics and…
kubernetes
Deploy, manage, and debug Kubernetes in production — Deployments, Services, Gateway API, Service Mesh (Istio/Linkerd/Cilium), eBPF observability (Cilium Hubble), security hardening (Pod Security Standards, OPA/Kyverno, seccomp, runtime security with Falco/Tetragon), Helm, HPA, PDB, topology spread, and debugging. Use…
cloud-monitoring
Monitor cloud infrastructure and applications using metrics, logs, and traces to provide real-time observability into performance, health, and reliability. Use when the user requests cloud monitoring or provides relevant inputs for this workflow.