Wiki / Packs / Hermes
claims at or below doctor Try it free

Hermes pack

Setup guide for Hermes — command-first. This page is the short path to try today; deeper notes live on GitHub if you need them.

Honesty: this pack is for day-to-day coding directions only — not the full security audit tool set. Connecting the pack does not by itself mean multi-helper (L3) work is production-finished. Check ceiling with knosky doctor.

1 · Map locally

npx knosky.

Node 20+ · current folder · local-first. Produces .knosky/city-data.json (and city.html).

Note: registry npx knosky may still resolve an older package until npm publishes 0.7 Mode B. Clone/main path always works.

2 · Mode B lease (governed tools)

node bin/knosky.mjs agent-register --domain.knosky --agent hermes-local --role coder

Pass the returned leaseId into kc_route / kc_policy_check / kc_bundle. Bare agentId cannot mint identity.

3 · MCP config

Point your host at mcp/server.mjs with absolute paths:

{
 "mcpServers": {
 "knosky": {
 "command": "node",
 "args": ["ABS/PATH/TO/knosky/mcp/server.mjs"],
 "env": {
 "KC_CITY": "ABS/PATH/TO/.knosky/city-data.json",
 "KC_PROFILE": "coding"
 }
 }
 }
}

Optional skill: repo packs/hermes/SKILL.md — MCP still does the real routing.

Coding path tools : map tools plus kc_route, kc_bundle, kc_policy_check. Not on coding: audit tools.

4 · Prove a route

Using KnoSky, route me to where authentication or billing is implemented.
Prefer a guided path — not a free monorepo walk. Use Mode B if leased.

5 · Honest limits

npx knosky doctor

L3 multi-agent = foundation module unless doctor reports full L3 green for this domain. Windows: do not claim kernel no-egress if doctor warns.