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 rhtevan/agentfs --skill hermes-agentfs-setupgit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/rhtevan/agentfs/hermes-agentfs-setup)<a href="https://agentmods.dev/skills/rhtevan/agentfs/hermes-agentfs-setup"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/hermes-agentfs-setup/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/rhtevan/agentfs/hermes-agentfs-setup"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/hermes-agentfs-setup.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01505 |
| Opus 5.5 | $0.00009 | $0.00602 |
| Sonnet 5.5 | $0.00005 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
hermes-agentfs-setup 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 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.
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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Agent — AgentFS Compatibility Setup
Configure Hermes Agent so it discovers AgentFS skills, making the same skill library available to both Goose and Hermes without duplication.
Problem
AgentFS stores skills at two levels:
| Scope | Path | Goose | Hermes (default) |
|---|---|---|---|
| USER | ~/.agents/skills/ |
✅ native | ❌ not scanned |
| PROJECT | .agents/skills/ (CWD) |
✅ native | ❌ not scanned |
Hermes only scans ~/.hermes/skills/ by default. It supports additional
paths via skills.external_dirs in ~/.hermes/config.yaml, but nothing
is configured out of the box.
What This Skill Fixes
USER scope — adds ~/.agents/skills to skills.external_dirs so
Hermes discovers every SKILL.md under ~/.agents/skills/ alongside its
own ~/.hermes/skills/.
PROJECT scope — registers a specific project's .agents/skills/
directory (as an absolute path) in skills.external_dirs. This is a
per-project action because Hermes has no CWD-relative skill scanning —
there is no way to configure a single relative path that follows the
working directory. Each project must be registered individually.
Compatibility Matrix (After Setup)
| Feature | Goose | Hermes |
|---|---|---|
AGENTS.md from CWD |
✅ native (default #1) | ✅ native (priority #2) |
~/.agents/skills/ (USER) |
✅ native | ✅ via external_dirs |
.agents/skills/ (PROJECT) |
✅ native (auto) | ✅ via external_dirs (manual per-project) |
| SKILL.md format | ✅ YAML frontmatter | ✅ same format |
Prerequisites
- Hermes Agent installed (
~/.hermes/exists withconfig.yaml) - AgentFS initialized (
~/.agents/skills/exists — runagentfs-setupskill in USER scope if needed)
Steps
Step 1: Check Current Compatibility
bash ~/.agents/skills/hermes-agentfs-setup/scripts/setup.sh --check
Reports USER and PROJECT status, registered project paths, and any issues to fix.
Step 2: USER Setup
bash ~/.agents/skills/hermes-agentfs-setup/scripts/setup.sh
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.
- 1mo ago First seen · 181 lines · 23 tokens per session scan A 977859b8dd4a
hermes-agentfs-setup is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,505 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…