Borrowing it
Nothing to install: this file belongs to gtapps/claude-code-hermit. 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/gtapps/claude-code-hermit/main/AGENTS.mdgit clone --depth 1 https://github.com/gtapps/claude-code-hermitWrote 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/gtapps/claude-code-hermit/agents-md)<a href="https://agentmods.dev/instructions/gtapps/claude-code-hermit/agents-md"><img src="https://agentmods.dev/badge/instructions/gtapps/claude-code-hermit/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.01477 | $0.01477 |
| Opus 5 | $0.00739 | $0.00739 |
| Sonnet 5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
claude-code-hermit 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 today.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidelines
Before changing a plugin, read its plugins/<slug>/AGENTS.md. Load only the guides for the work in scope. Local guides add constraints to these repository rules; detailed inventories and procedures belong in READMEs, docs, or skills. Keep AGENTS.md and CLAUDE.md independently readable, with no extra instruction-file hop between harnesses.
Repository and architecture
- Seven independently versioned Claude Code plugins live under
plugins/<slug>/, each owning its manifest, code, templates, tests, and changelog..claude-plugin/marketplace.jsonis the sole catalog;README.mdis the marketplace overview. - Hermit runs continuously inside Claude Code. Evaluate features for downstream chat operators, not only this repository's development workflow. Check native harness capabilities before adding a competing mechanism.
- Domain plugins depend on core. Core discovers siblings generically from metadata; it must not import siblings, hardcode their slugs in logic, or branch on their installation. Siblings use core commands with an appropriate version floor instead of importing core code. Preserve
${CLAUDE_PLUGIN_ROOT}/../*/.claude-plugin/plugin.jsondiscovery. - Domain plugin
skills/,agents/,state-templates/, anddocs/carry core-facing terminology; sweep them when core wording changes. - Keep
required_core_versionandrequiresin.claude-plugin/hermit-meta.jsonsynchronized withplugin.jsondependencies. Internalhermit.*extensions belong in hermit-meta.json. Raisemin_claude_code_versionwhen relying on newer host behavior; do not add old-host shims.
Authoring contracts
- Keep schemas, permissions, hook protocols, and command interfaces strict; keep operator-authored content flexible and upgrade-safe. Features default on except those requiring credentials/configuration, real per-invocation spend, or destructive actions. Cover new and existing installations.
- Skills state the present inputs, goal, workflow, and result. Keep history in changelogs or code comments and branch-specific detail in referenced sibling files. Use fully namespaced plugin agent references.
- Hook stdout, tool output, and skill-driven reads enter operator context. Use scripts for deterministic work and bounded log/database summaries; do not ask the model to read unbounded state or reproduce calculations.
state-templates/CLAUDE-APPEND.mdis installed product content, separate from development instructions. Describe behavior there without restating config values such as schedules, channel IDs, identity, or mode flags.- Core's
scripts/domain-hatch.tsandlib/domain-hatch/own target resolution andstate/hatch-options.json. Consumers usedomain-hatch preflight,ensure-target, andsync-block; read those contracts before changing routing. - Before changing plugin storage or routine registration, read the storage contract or routine authoring, respectively.
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.
- today First seen · 57 lines · 1,477 tokens per session scan A 4e5533894f1e
claude-code-hermit AGENTS.md is an instructions file published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed yesterday), licensed MIT. It adds 1,477 tokens to every session, about $0.0074 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-09-06.
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.