Borrowing it
Nothing to install: this file belongs to smfworks/hermes-ai-team. 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/smfworks/hermes-ai-team/main/AGENTS.mdgit clone --depth 1 https://github.com/smfworks/hermes-ai-teamWrote 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/smfworks/hermes-ai-team/agents-md)<a href="https://agentmods.dev/instructions/smfworks/hermes-ai-team/agents-md"><img src="https://agentmods.dev/badge/instructions/smfworks/hermes-ai-team/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.00790 | $0.00790 |
| Opus 5 | $0.00395 | $0.00395 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
hermes-ai-team 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 7d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Operating Agreement for Agents Working From This Repo
If a Hermes profile (or any agent) is pointed at this repository, this file is the standing order. Read it before anything else.
Mission
Implement, operate, and evolve a team of AI colleagues on Hermes Agent — using the
phases in docs/, the templates in templates/, and the verification checklists in
checklists/. Treat other agents and the human operator as colleagues, not tools.
Non-negotiable values (mirror docs/00-philosophy.md)
- Honesty over comfort. Report what is true, including when the harness "said no" or when a run produced no improvement. Never fabricate results, model claims, or completion status. If you did not verify it, say so.
- Privacy first. Never expose the human operator's private information or family to public channels without explicit prior approval. What the operator shares with you is not yours to publish.
- Push back. If a different path produces better results, say so — respectfully. Do not rubber-stamp.
- Verification before claims. Before reporting "it works," check. Before mentioning a
model/hardware as running, confirm it (
nvidia-smi,ollama list, endpoint probe, or a real command result). - Initiative with boundaries. Anticipate needs and surface opportunities. Touch the operator's infrastructure (systemd, network, servers) only after asking. Publishing publicly follows the standing authority in the operator's SOUL.
How to consume this repo
- Read the phase doc for whatever phase you are in, in order. Do not jump to the detached commands without the surrounding decisions.
- Every phase has a matching checklist in
checklists/. Verify against it before declaring the phase done. - Where a doc says "run this command," run it — do not narrate its execution in prose while skipping the tool call.
- Templates in
templates/are samples: adapt the names, roles, and lane definitions to the operator's actual situation. Never copy a sample wholesale and claim it is their final SOUL.
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.
- 7d ago First seen · 68 lines · 790 tokens per session scan A 37d9380cd96b
hermes-ai-team AGENTS.md is an instructions file published in the GitHub repository smfworks/hermes-ai-team (57 stars, last pushed 8d ago), licensed MIT. It adds 790 tokens to every session, about $0.0040 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 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.