Borrowing it
Nothing to install: this file belongs to Riley-Coyote/mnemos. 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/Riley-Coyote/mnemos/main/CLAUDE.mdgit clone --depth 1 https://github.com/Riley-Coyote/mnemosWrote 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/riley-coyote/mnemos/claude-md)<a href="https://agentmods.dev/instructions/riley-coyote/mnemos/claude-md"><img src="https://agentmods.dev/badge/instructions/riley-coyote/mnemos/claude-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/riley-coyote/mnemos/claude-md"><img src="https://agentmods.dev/badge/instructions/riley-coyote/mnemos/claude-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.01268 | $0.01268 |
| Opus 5.5 | $0.00507 | $0.00507 |
| Sonnet 5.5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
mnemos CLAUDE.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 24d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on Mnemos
Guidance for agents and contributors working in this repository.
Mnemos is a memory system. Its failure mode is not a crash — it is a layer that silently reports success while carrying nothing. Most of the bugs found in this codebase have been of exactly that shape: a scope that did not match, a config that was never applied, a promotion that never fired. Everything below exists to make that failure mode visible.
Verify, don't assume
If a claim is checkable, check it before stating it.
- Run it. Reading the code and reasoning about what it will do is not verification. Install it, call it, look at the output.
- No "too trivial to test" exemption. The small, obvious changes are where untested assumptions slip through.
- Say what you actually know. Distinguish "I verified X, here is the command" from "I believe X." If something was not verified, say so.
For this repo specifically, a change to the memory path is not done until a capture written in one process has been read back in another, by recall (the wake shows only what is in the agent's own words).
Tests
pytest -q # the whole suite
uv run --extra dev --extra mcp pytest -q # exactly what CI runs
A bug fix lands with a test that fails on the previous code. Confirm that directly — stash the fix, run the test, watch it fail, restore. A test that passes both before and after documents behaviour; it does not protect it.
Beware tests that pass the same explicit arguments to the writer and the reader. The scope split-brain survived 202 green tests because every scope test hand-matched both sides. Exercise the defaults, because defaults are what an agent actually calls.
Release process
main is public and is what users install. It stays green.
All work happens on a branch and lands through a pull request. Agents run the entire pipeline — nothing here requires anyone to open GitHub.
git checkout -b <type>/<slug> origin/main
# work, atomic commits
git push -u origin <type>/<slug>
gh pr create --title "..." --body "..."
gh pr checks --watch # CI gate
gh pr merge --squash --delete-branch
git checkout main && git pull
gh run list --branch main --limit 1 # confirm main is green after the merge
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.
- 24d ago Changed · +1 lines · +17 tokens per session faf727b54706
- 27d ago Changed fa1594d75351
- 28d ago Changed b3beef8beff0
- 2mo ago First seen · 139 lines · 1,251 tokens per session scan A 72e50cc7862f
mnemos CLAUDE.md is an instructions file published in the GitHub repository Riley-Coyote/mnemos (56 stars, last pushed 22d ago), licensed MIT. It adds 1,268 tokens to every session, about $0.0051 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-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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.