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/rustkit-ai/aimemo/claude-mdgit clone --depth 1 https://github.com/rustkit-ai/aimemoWhat 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.00099 | $0.00099 |
| Opus 5 | $0.00049 | $0.00049 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade D, and why
aimemo CLAUDE.md scanned grade D with 2 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 2d 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.
<!-- aimemo:instructions:start --> Whitespace paddingmediumPrompt injection
A block of blank lines or a long run of spaces can push injected text below or beside what a reviewer sees, while the model still reads it.
<!-- aimemo:instructions:start --> What it actually says
aimemo context
last: (no entries yet)
aimemo — persistent memory
- Run
aimemo injectat the start of every session to recall context - Run
aimemo log "<what you did>"after each significant task - Run
aimemo log "todo: <next step>"before ending the session
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.
- 2d ago First seen · 53 lines · 99 tokens per session scan D a7009d4759c3
aimemo CLAUDE.md is an instructions file published in the GitHub repository rustkit-ai/aimemo (4 stars, last pushed 5mo ago), licensed MIT. It adds 99 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it D with 2 findings (hidden instructions, whitespace padding). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
mcp-unity AGENTS.md
Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
DebugMCP AGENTS.md
Instructions for microsoft/DebugMCP, covering agent guidelines for debugmcp, project overview, architecture, key components and documentation maintenance.
memorix GEMINI.md
Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
awesome-reviewers CLAUDE.md
Instructions for baz-scm/awesome-reviewers, covering awesome reviewers — repository guidelines, what this project is, source of truth, site layer and machine interface.
slack-mcp-server CLAUDE.md
Instructions for jtalk22/slack-mcp-server, covering claude.md, project scope, build and run, installation paths and mcp tools (19 total).