Borrowing it
Nothing to install: this file belongs to felipesauer/mnema. 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/felipesauer/mnema/main/AGENTS.mdgit clone --depth 1 https://github.com/felipesauer/mnemaWrote 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/felipesauer/mnema/agents-md)<a href="https://agentmods.dev/instructions/felipesauer/mnema/agents-md"><img src="https://agentmods.dev/badge/instructions/felipesauer/mnema/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/felipesauer/mnema/agents-md"><img src="https://agentmods.dev/badge/instructions/felipesauer/mnema/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00707 | $0.00707 |
| Opus 5.5 | $0.00283 | $0.00283 |
| Sonnet 5.5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
mnema 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 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notes for an agent changing this repository
This is the short list of what an agent gets wrong here first. What the product is lives on
the front page; the full contributor guide is CONTRIBUTING.md.
Run the gates, in this order, on what you committed
pnpm install --frozen-lockfile
pnpm build
pnpm lint
pnpm typecheck
pnpm test
pnpm build comes before pnpm typecheck and pnpm test: the packages compile against each
other's built output, so a stale dist makes both go green over code that no longer exists.
When a case is red, keep the output, then run pnpm why-it-went-red: it says whether the
guard caught a defect or the machine was busy.
Commits and pull requests
- Branch, commit message and pull request in English, descriptive: what changes, as a sentence.
- Commit with a
users.noreply.github.comaddress, not a work or personal one (git config user.emailshows which you will use). - No
Co-Authored-Bytrailer and no generated-with footer: thethe-link-cannot-come-backjob fails on them. If an agent wrote the change, say which model, host and version in the field the pull request template asks for. - One change per pull request. Add files by path; never
git add -Aorgit add ..
Where the tests are
Product tests are in packages/*/tests/, named for the behaviour they hold. A new file under
packages/*/src needs a test that asserts about a value it produced, and a new test file needs
its line in every-file-has-a-test-that-names-it.test.ts. pnpm typecheck checks the tests
too (each package's tsconfig.test.json), but vitest strips types when it runs them, so a type
is never what makes a test fail: assert on a value, never on a type guard. A new guard comes
with a case that shows it failing on the defect it exists for.
Skills
A change to a skill in plugin/skills/ needs an eval: prompts that must bring the skill up and
prompts that must not, and what a real run did with each. No automated eval exists yet; the test
named every-skill-the-plugin-ships-is-what-it-says checks only the skill's form. The details are
in CONTRIBUTING.md.
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 Changed · +1 lines · +8 tokens per session 039fda5bcebb
- 8d ago Changed · -2 tokens per session de0ee9fbf695
- 10d ago Changed · +8 lines · +134 tokens per session 540f2e344d2e
- 13d ago First seen · 51 lines · 567 tokens per session scan A 9cb1bf3712cd
mnema AGENTS.md is an instructions file published in the GitHub repository felipesauer/mnema (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 707 tokens to every session, about $0.0028 per session on Opus 5.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-10-03.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).