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/asimons81/hermes-field-kit/skill-templatenpx skills add asimons81/hermes-field-kit --skill skill-templategit 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/skill-template)<a href="https://agentmods.dev/skills/asimons81/hermes-field-kit/skill-template"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/skill-template.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.00028 | $0.00223 |
| Opus 5 | $0.00014 | $0.00112 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
replace-with-skill-name 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.
What it actually says
Replace with Skill Title
TEMPLATE ONLY. Replace every placeholder before moving this directory to
skills/<skill-name>/.
Overview
Describe the recurring task and the process discipline this skill adds.
When to Use
Use this skill when:
- REPLACE_WITH_A_POSITIVE_TRIGGER
Do not use this skill when:
- REPLACE_WITH_A_COUNTER_TRIGGER
Workflow
- REPLACE_WITH_AN_ACTION_AND_A_CHECKABLE_COMPLETION_CRITERION.
Common Pitfalls
- REPLACE_WITH_A_FAILURE_MODE. Explain the correction.
Verification Checklist
- REPLACE_WITH_AN_OBSERVABLE_RESULT
What ships with it
3 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.
- 6d ago First seen · 44 lines · 28 tokens per session scan A 335e7e839deb
replace-with-skill-name is a skill published in the GitHub repository asimons81/hermes-field-kit (124 stars, last pushed 17d ago), licensed Apache-2.0. It adds 28 tokens to every session and 223 once invoked, about $0.0001 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
soul-grader
Use when grading, reviewing, rewriting, or approving a Hermes Agent SOUL.md. Uses the SOUL.md field-guide research artifacts as the only normative source for what makes a good SOUL.md.
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.
implement
Execute approved Hardproof tasks during IMPLEMENT with focused tests, durable task updates, and scope-controlled code changes.
learn
Close a Hardproof run during LEARN by capturing safe provenance-linked lessons or recording an explicit reason to skip them.