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/nousresearch/hermes-agent/honchonpx skills add NousResearch/hermes-agent --skill honchogit clone --depth 1 https://github.com/NousResearch/hermes-agentWhat 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.00012 | $0.04628 |
| Opus 5 | $0.00006 | $0.02314 |
| Sonnet 5 | $0.00002 | $0.00926 |
| Haiku 4.5 | $0.00001 | $0.00463 |
Grade A, and why
honcho 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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- honcho — 100% identical, 0 lines differ
- honcho — 100% identical, 0 lines differ
- honcho — 100% identical, 0 lines differ
- honcho — 98% identical, 7 lines differ
- honcho — 98% identical, 7 lines differ
- honcho — 97% identical, 2 lines differ
- honcho — 97% identical, 2 lines differ
- honcho — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Honcho Memory for Hermes
Honcho provides AI-native cross-session user modeling. It learns who the user is across conversations and gives every Hermes profile its own peer identity while sharing a unified view of the user.
When to Use
- Setting up Honcho (cloud or self-hosted)
- Troubleshooting memory not working / peers not syncing
- Creating multi-profile setups where each agent has its own Honcho peer
- Tuning observation, recall, dialectic depth, or write frequency settings
- Understanding what the 5 Honcho tools do and when to use them
- Configuring context budgets and session summary injection
Setup
Cloud (app.honcho.dev)
hermes memory setup honcho
# select "cloud", paste API key from https://app.honcho.dev
Self-hosted
hermes memory setup honcho
# select "local", enter base URL (e.g. http://localhost:8000)
See: https://docs.honcho.dev/v3/guides/integrations/hermes#running-honcho-locally-with-hermes
Verify
hermes honcho status # shows resolved config, connection test, peer info
Architecture
Base Context Injection
When Honcho injects context into the system prompt (in hybrid or context recall modes), it assembles the base context block in this order:
- Session summary -- a short digest of the current session so far (placed first so the model has immediate conversational continuity)
- User representation -- Honcho's accumulated model of the user (preferences, facts, patterns)
- AI peer card -- the identity card for this Hermes profile's AI peer
The session summary is generated automatically by Honcho at the start of each turn (when a prior session exists). It gives the model a warm start without replaying full history.
Cold / Warm Prompt Selection
Honcho automatically selects between two prompt strategies:
| Condition | Strategy | What happens |
|---|---|---|
| No prior session or empty representation | Cold start | Lightweight intro prompt; skips summary injection; encourages the model to learn about the user |
| Existing representation and/or session history | Warm start | Full base context injection (summary → representation → card); richer system prompt |
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.
- yesterday First seen · 432 lines · 12 tokens per session scan A 7623d663cb5e
honcho is a skill published in the GitHub repository NousResearch/hermes-agent (238,457 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 4,628 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
keybindings-help
Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify /.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
options
Present multiple design options as a vertical stack of anchored turns.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.