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 asimons81/hermes-field-kit --skill hermes-environment-migrationgit clone --depth 1 https://github.com/asimons81/hermes-field-kitWrote 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/asimons81/hermes-field-kit/hermes-environment-migration)<a href="https://agentmods.dev/skills/asimons81/hermes-field-kit/hermes-environment-migration"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/hermes-environment-migration/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/asimons81/hermes-field-kit/hermes-environment-migration"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/hermes-environment-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high YARA Match · line 59 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00036 | $0.01709 |
| Opus 5 | $0.00018 | $0.00855 |
| Sonnet 5 | $0.00007 | $0.00342 |
| Haiku 4.5 | $0.00004 | $0.00171 |
Grade A, and why
hermes-environment-migration 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hermes-environment-migration
Overview
A platform-aware migration protocol that refuses blind copies of machine-bound state and separates ordinary configuration from credentials and encrypted vault material.
The skill is evidence-first. It identifies unavailable evidence, separates facts from interpretations, and does not claim a repair or successful outcome merely because a command returned without an obvious error.
When to Use
- Move my Hermes setup to a new machine.
- Prepare a Hermes migration export.
- Verify and import this Hermes archive.
- Migrate profiles, skills, memory, and cron safely.
Counter-Triggers
Do not load this skill when:
- The user only wants to install a fresh Hermes instance.
- The request is a generic file copy with no Hermes state.
- The archive cannot be staged and verified before import.
Safety Contract
- Back up the target before any import.
- Never display or include secrets in the ordinary migration archive.
- Never activate an imported session database blindly.
- Stage and verify archives outside live Hermes directories.
- Reject path traversal, absolute archive paths, hash mismatches, and unexpected files.
- Import cron jobs disabled and gateway configuration inactive until reviewed.
- Stop on integrity failures and preserve rollback artifacts.
- Never invent names, paths, versions, counts, component identities, or other specifics that are absent from the supplied evidence.
- When evidence provides only an aggregate, preserve that aggregate exactly, such as
three local skills (names not provided), rather than supplying plausible examples. - Treat evidence labels narrowly. A
clean SHA-256 manifestproves only the explicitly stated hash result; it does not prove manifest scope, absence of orphan files, signatures, provenance, archive safety, or lack of tampering unless those checks were separately supplied.
Any mutation, repair, persistence, publication, credential change, process change, repository write, or external side effect mentioned by this skill requires a separate explicit approval after the diagnostic or planning output.
What ships with it
9 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.
- 9d ago First seen · 184 lines · 36 tokens per session scan A 0a5d15f56c20
hermes-environment-migration is a skill published in the GitHub repository asimons81/hermes-field-kit (125 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,709 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
implement
Execute approved Hardproof tasks during IMPLEMENT with focused tests, durable task updates, and scope-controlled code changes.
orchestrate
Coordinate an active Hardproof run across discovery, design, planning, implementation, review, verification, delivery, and learning.
deliver
Prepare an inspectable Hardproof delivery during DELIVER with final scope, evidence, risks, rollback, and reproducible reporting.
design
Shape the smallest reversible Hardproof design from discovery evidence during DESIGN, including contracts, failures, and risks.
discover
Inspect a Hardproof run's request, repository, constraints, and unknowns during DISCOVERY before proposing a design.
learn
Close a Hardproof run during LEARN by capturing safe provenance-linked lessons or recording an explicit reason to skip them.