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/good-v1be/simple-rick/claude-mdgit clone --depth 1 https://github.com/good-v1be/simple-rickWrote 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/good-v1be/simple-rick/claude-md)<a href="https://agentmods.dev/instructions/good-v1be/simple-rick/claude-md"><img src="https://agentmods.dev/badge/instructions/good-v1be/simple-rick/claude-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.01068 | $0.01068 |
| Opus 5 | $0.00534 | $0.00534 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
simple-rick 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for AI agents working on this repository.
What this is
Simple Rick is a local MCP server that gives coding agents persistent memory. It records sessions, normalizes them into embedded chunks, wires those into a graph, and serves the relevant context back at the start of the next session. See README.md for the user-facing documentation.
Tech stack
- Runtime: Node.js 20+, TypeScript (ESM,
"type": "module"— imports need the.jsextension) - Interface: MCP over stdio (
@modelcontextprotocol/sdk) - Database: SQLite via
better-sqlite3, vectors viasqlite-vec - AI providers: auto-detected — OpenAI, Google, Mistral, or Anthropic + Voyage (
services/ai-providers.ts) - File watching: chokidar
- Tests: Vitest
Critical constraints
Never write to stdout. MCP speaks JSON-RPC over stdout; a single console.log corrupts the protocol. src/server/index.ts reassigns console.log = console.error on its first line, above all imports. Keep that line where it is, and route logging through log.ts (see below).
Schema changes go through the migration runner. src/server/db/sqlite.ts applies schema.sql, then db/migrate.ts applies anything newer than the version recorded in schema_migrations. To change the schema, append an entry to MIGRATIONS — never edit or reorder an existing one, its version is already recorded in databases in the wild.
LLM output is never trusted directly. Parse it through services/ai-json.ts (extractObject, extractArray, asString, asInt, asEnum, asStringArray, filterValid). Those helpers coerce and log rather than throw, because one malformed model response must not take down the pipeline. Do not reintroduce bare JSON.parse(raw) ?? {}.
Errors get logged. Use log.ts (logError/logWarn/logInfo/logDebug) instead of console.error, and do not write a bare catch {} — pick a level: expected-and-noisy is debug, unexpected is warn or error.
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.
- 4d ago First seen · 82 lines · 1,068 tokens per session scan A 71f0abb338cc
simple-rick CLAUDE.md is an instructions file published in the GitHub repository good-v1be/simple-rick (0 stars, last pushed 8d ago), licensed MIT. It adds 1,068 tokens to every session, about $0.0053 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-31.
Other instructions, from other repositories
cli AGENTS.md
Instructions for konteks/cli, covering agent instructions, project overview, tech stack, repository layout and common commands.
remnic AGENTS.md
AGENTS.md instructions for joshuaswarren/remnic, covering remnic - agent guide, architecture boundaries (non-negotiable), upstream references, adapter implementation rules and openclaw compatibility window.
sibyl CLAUDE.md
Claude Code instructions for hyperb1iss/sibyl, covering sibyl development guide, project overview, sibyl integration, always use skills and research → do → reflect cycle.
Dragon-Brain CLAUDE.md
Instructions for iikarus/Dragon-Brain, covering dragon brain — claude.md, the harness, audit remediation (april–may 2026, complete 2026-05-09), the lie this audit closed and the contract that matters now.
engram-mcp CLAUDE.md
Claude Code instructions for edg-l/engram-mcp, covering engram mcp, development rules, structure, key types and mcp capabilities.
brainlayer AGENTS.md
Instructions for EtanHey/brainlayer, covering brainlayer — a letter from etan, brainlayer agent notes (operational), review guidelines, key paths and database.