Borrowing it
Nothing to install: this file belongs to mmnto-ai/totem. 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/mmnto-ai/totem/main/AGENTS.mdgit clone --depth 1 https://github.com/mmnto-ai/totemWrote 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/mmnto-ai/totem/agents-md)<a href="https://agentmods.dev/instructions/mmnto-ai/totem/agents-md"><img src="https://agentmods.dev/badge/instructions/mmnto-ai/totem/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.01585 | $0.01585 |
| Opus 5 | $0.00792 | $0.00792 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade C, and why
totem AGENTS.md scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- totem-ignore-next-line --> How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Totem: Agent Instructions
Canonical source of truth for how AI coding agents (Claude Code, Gemini CLI, Cursor, etc.) behave in this repo. Per Totem ADR-038 (mmnto-ai/totem-strategy:adr/adr-038-agents-md-standard.md), mmnto-ai/totem consolidates tool-specific instruction files into this single AGENTS.md. Thin CLAUDE.md / GEMINI.md redirects point each tool here.
What Totem is
Totem is a deterministic, git-native governance toolkit — rules you enforce, state you derive, context you query. Lead with enforcement (totem lint + the gate engine), not recall. Derivation (totem status / orient, Tenet 20) and the queryable index serve it.
Session Start Protocol (MANDATORY)
- Run
totem statusfor health. - NEVER GUESS ARCHITECTURE. Before modifying any core system, run
totem search <system_name>. - Before writing code, call
search_knowledgedescribing what you're changing. - Before planning, query
totem-strategy:search_knowledgefor ADRs. - Don't push speculative fixes. Run
totem lintlocally — front-load all checks before the first push.
Essentials
- pnpm only (never npm/yarn). Use
pnpm dlx(nevernpx). TypeScript strict mode. mainis protected. Feature branches + PRs. Never amend commits on feature branches. UseCloses #NNNin PR descriptions.kebab-case.tsfiles,err(nevererror) in catch blocks, no empty catches.- Named constants for magic numbers. Zod at system boundaries only.
- NEVER put secrets in config files.
.envonly. - Totem is NOT zero-user. Ships in production for downstream consumers beyond this repo's dogfood. Breaking changes need migration paths, not just "fix in next major."
Totem Workflow
Not mechanically enforced. Follow because they reduce PR bot noise.
- Before coding:
/preflight <issue>. Create a feature branch. - Before pushing:
pnpm run format→totem lint→totem review→ verify compile manifest is current. - After merging a PR:
totem lesson extract <pr> --yes. - NEVER bypass quality gates without a ticket. No
--no-verify,totem-ignore,eslint-disable,@ts-ignore, skipped tests, or CI-pacifying ignore patterns. Suppressions need a ticket-ref comment. - Open PRs Ready, not Draft. Ready signals review-readiness for the operator's trigger word (strategy#622).
- Vendor routing. Claude is the default code executor; Gemini stays strategic (proposals, ADRs, audits). Cross-vendor second-opinion fine both ways; "Gemini implement" is not the default.
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 · 86 lines · 1,585 tokens per session scan C 65e6473cef45
totem AGENTS.md is an instructions file published in the GitHub repository mmnto-ai/totem (17 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,585 tokens to every session, about $0.0079 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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.
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).
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.