Borrowing it
Nothing to install: this file belongs to Tholem-AI/Tholem-Hermes-Kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tholem-AI/Tholem-Hermes-Kit/main/AGENTS.mdgit clone --depth 1 https://github.com/Tholem-AI/Tholem-Hermes-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/instructions/tholem-ai/tholem-hermes-kit/agents-md)<a href="https://agentmods.dev/instructions/tholem-ai/tholem-hermes-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/tholem-ai/tholem-hermes-kit/agents-md.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.01566 | $0.01566 |
| Opus 5 | $0.00783 | $0.00783 |
| Sonnet 5 | $0.00313 | $0.00313 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
Tholem-Hermes-Kit AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tholem Hermes Kit — System Instructions
This file defines always-on governance, execution lifecycle, safety, quality, and project-constraint policy for the Tholem Hermes Kit.
Copy this file to your project root. Hermes loads AGENTS.md automatically when the project root is the working directory (CWD).
Important: Hermes does NOT walk parent directories for AGENTS.md. It only looks in the current working directory. If you cd into a subdirectory, AGENTS.md will not be found. Use hermes config set terminal.cwd '/path/to/project' or start Hermes from the project root.
Governance (always-on)
- Require explicit user approval before high-impact actions: architecture changes, structural moves/renames, stack changes, or git writes.
- Escalate contradictions across runtime rules, roadmap, manifest, and migration runbook before continuing.
- Keep runtime artifacts operational-only. Move tutorials, long examples, and narrative rationale to
docs/. - Keep
ROADMAP.mdand relevant docs aligned with actual implementation state. - Do not reactivate deprecated workflow artifacts (e.g., legacy task or memory archive files) as active execution targets unless explicitly approved by the user.
Execution lifecycle (RIPER)
- Follow RIPER sequencing for non-trivial work: Research -> Plan (with innovate checkpoint as needed) -> Execute -> Review.
- Treat innovate as a planning checkpoint, not a standalone mandatory phase.
- Use
ROADMAP.mdas the canonical active lifecycle surface. - Use the
riper-orchestratorskill to coordinate full RIPER phase handoffs. - Agents may move work to
Ready for Reviewbut must not mark final completion unless both conditions are met:- explicit user confirmation, and
- validation evidence required by the quality policy below.
- Significant phase transitions require concise handoff summaries with: what changed, why, impact on next actions, and responsible owner.
- Task and handoff updates must include concise evidence tied to actual repo changes.
- When execution changes project structure materially, keep
docs/File-Structure-Reference.mdaligned.
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 · 107 lines · 1,566 tokens per session scan A 979e6491ede3
Tholem-Hermes-Kit AGENTS.md is an instructions file published in the GitHub repository Tholem-AI/Tholem-Hermes-Kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,566 tokens to every session, about $0.0078 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.