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/harshanandak/forge/hermes-forgenpx skills add harshanandak/forge --skill hermes-forgegit clone --depth 1 https://github.com/harshanandak/forgeWrote 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/harshanandak/forge/hermes-forge)<a href="https://agentmods.dev/skills/harshanandak/forge/hermes-forge"><img src="https://agentmods.dev/badge/skills/harshanandak/forge/hermes-forge.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 | $0.00232 | $0.02127 |
| Opus 5 | $0.00116 | $0.01064 |
| Sonnet 5 | $0.00046 | $0.00425 |
| Haiku 4.5 | $0.00023 | $0.00213 |
Grade A, and why
hermes-forge 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes ⇄ Forge consumption contract
Hermes is a consumer of Forge project state, not an owner of it. This skill defines how a Hermes session reads, cites, and writes back to a Forge project without ever becoming a second source of truth.
The boundary between what Forge owns and what Hermes owns is specified in the
Forge repo at docs/reference/HERMES_INTEGRATION.md (repo-relative path — this
skill is synced to .hermes/skills/hermes-forge/, so relative links would not
resolve from the installed location).
When to use
- At the start of any Hermes session on a Forge repo (orientation).
- Before acting on a specific issue (issue recap).
- Whenever you need current project state — never reconstruct it from raw files.
Authority: orient / recap are the only state source
The Forge Kernel is the single source of truth. Hermes obtains project state exclusively through two thin CLI wrappers and must not infer state by reading raw issue stores, design files, or kernel internals directly:
forge orient --json # bounded project orientation (envelope)
forge orient --budget 4000 --json
forge recap <issue-id> --json # bounded per-issue recap (envelope)
forge orient and forge recap <issue-id> emit the deterministic JSON envelope
described below (assembly deterministic-file-assembly-v1). Parse the JSON; do
not screen-scrape the human text form.
Note:
forge recapalways requires an issue id — bareforge recap --json(no id) prints its usage and exits non-zero rather than returning a summary. Useforge orientfor project-level orientation, orforge recap <issue-id>for a single issue; both emit the deterministic envelope.
Envelope shape
| Field | Meaning |
|---|---|
schema_version |
Contract version (currently 1). Reject unknown majors. |
kind |
orientation, issue_recap, or prime. |
generated_at |
Assembly timestamp. |
assembly |
deterministic-file-assembly-v1 — same inputs ⇒ same output. |
token_budget |
Budget accounting (see below). |
sections[] |
Ordered content blocks, each independently cited. |
sources[] |
Deduplicated provenance across all sections. |
next_commands[] |
Suggested follow-up forge commands. Prefer these for navigation. |
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.
- 5d ago First seen · 187 lines · 232 tokens per session scan A 73e1d889e7d9
hermes-forge is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 5d ago), licensed MIT. It adds 232 tokens to every session and 2,127 once invoked, about $0.0012 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…