Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/wentout/mnemonica/agents-mdgit clone --depth 1 https://github.com/wentout/mnemonicaWrote 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/wentout/mnemonica/agents-md)<a href="https://agentmods.dev/instructions/wentout/mnemonica/agents-md"><img src="https://agentmods.dev/badge/instructions/wentout/mnemonica/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 | $0.04048 | $0.04048 |
| Opus 5 | $0.02024 | $0.02024 |
| Sonnet 5 | $0.00810 | $0.00810 |
| Haiku 4.5 | $0.00405 | $0.00405 |
Grade A, and why
mnemonica 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 3d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance specific to mnemonica/core for AI agents
modifying the library itself. If you are using mnemonica in your own
project, start with README.md.
Before any subagent fan-out or swarm: read
.ai/SWARM.md. Stop-and-ask is mandatory there, exactly as in Rule #1 below.
Rule #1 — Non-negotiable: PAUSE AND ASK
This is the highest-priority rule. It overrides everything else in this file.
STOP and ask the user before proceeding when ANY of these is true:
- An error occurred —
Editfailed,Writeproduced unexpected results, or any tool returned an error. A successful retry does NOT cancel this rule: report the error AND how you recovered. - You are uncertain — about what change to make, how a function works, or what the user intended.
- You are filling gaps with assumption — "probably", "likely", "I think", "it should work" are signals to stop.
- A tool or environment constraint conflicts with the user's stated preference — surface the conflict verbatim; never silently satisfy the tool at the user's expense.
- You are about to create or duplicate a file the user did not
explicitly request — ask first. Never copy content when
mv, rename, or a reference suffices.
When in doubt: STOP, ask one clear specific question, WAIT for the answer.
Do not invent workarounds (no sed, no python -c, no console hacks,
no rewriting files to bypass a tool restriction).
Silent recovery is a violation, even when the outcome looks fine.
The reason this rule exists: wrong assumptions waste both your time and the
user's. The library encodes non-obvious design intent (data-flow vs control-flow,
define() semantics, the proxy architecture, the return-via-variable rule).
Confident guesses produce code that compiles but corrupts the design.
Note: Framework-agnostic rules are also available in
.ai/— start withONBOARDING.md(the quickstart); role notes for plan/answer/debug work are folded in there, andDEBUG.mdcovers debugger workflow. These rules apply to all agent frameworks.
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.
- 3d ago First seen · 343 lines · 4,048 tokens per session scan A 9d7c62450c66
mnemonica AGENTS.md is an instructions file published in the GitHub repository wentout/mnemonica (41 stars, last pushed 8d ago), licensed MIT. It adds 4,048 tokens to every session, about $0.0202 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.