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/azerv1/thimiko/claude-mdgit clone --depth 1 https://github.com/azerv1/thimikoWrote 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/azerv1/thimiko/claude-md)<a href="https://agentmods.dev/instructions/azerv1/thimiko/claude-md"><img src="https://agentmods.dev/badge/instructions/azerv1/thimiko/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.00945 | $0.00945 |
| Opus 5 | $0.00473 | $0.00473 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
thimiko 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
thimiko — agent guide
Layered, searchable memory over local Codex, Claude Code, GitHub Copilot, Gemini
CLI, Cursor, and OpenCode chat history. See ARCHITECTURE.md for the
layer/interface design before changing structure.
Commands
uv sync # create .venv + uv.lock
uv run thimiko build # full rebuild of the index (default: %LOCALAPPDATA%\thimiko\thimiko.sqlite)
uv run thimiko update [--prune] # incremental: only changed/new files; --prune drops deleted files' sessions
uv run thimiko search "query" # BM25 ranked search; JSON by default (--text for humans, --days N for recency)
uv run thimiko list [-v] # supported sources + roots; -v adds indexed/on-disk chat counts
uv run thimiko mcp # launch the MCP server over stdio
--db PATH overrides the index location on any subcommand.
Invariants (don't break these)
- Never merge providers' raw schemas — normalize into the canonical
Session/Eventmodel only. SeeARCHITECTURE.md. - Every
Eventcarries aProvenance(source file + line). Never lose that link — it's howget_turn/get_sessionpoint back to the raw record. - Only ordinary user/assistant
Messages aresearchable. Hidden reasoning, tool calls/results, and attachments stay out of the default search corpus. - FTS5 (
documents_fts) is kept in sync via triggers ondocuments, not a manual reindex step — if you touchSqliteStore, insert/delete throughdocuments, don't write todocuments_ftsdirectly. Store,Retriever, andChatSourceare ABCs for a reason: code above a layer must depend only on the interface (e.g.cli.py/mcp.pynever importsqlite3directly).- Provider databases are inputs, never index targets. In particular,
opencode.dbmust only be opened read-only as a source;--dbalways names Thimiko's separate derived SQLite index. - Capture
ChatSource.fingerprint()before parsing and record that exact value. OpenCode combines its main database and WAL so concurrent writes remain visible to the nextupdate.
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 · 70 lines · 945 tokens per session scan A bec92d4fd1de
thimiko CLAUDE.md is an instructions file published in the GitHub repository azerv1/thimiko (2 stars, last pushed 14d ago), licensed MIT. It adds 945 tokens to every session, about $0.0047 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
google_workspace_mcp general.instructions.md
Instructions for taylorwilsdon/google_workspace_mcp, covering 📄 project context, 🎯 review goals & priorities, 🚦 low‑value feedback to skip, 🧭 review structure template and ✅ gmail.sendmessage – input schema issue.
mirascope AGENTS.md
AGENTS.md instructions for Mirascope/mirascope, covering ai agent context guide, primary context sources, codebase overview, key principles and quick reference.
Ix CLAUDE.md
Claude Code instructions for ix-infrastructure/Ix, covering project: ix (this repo), layout, commands, cli dev (from ix-cli/) and skill + tooling (from repo root).
automem CLAUDE.md
Instructions for verygoodplugins/automem, covering claude.md, project overview, development commands, setup environment and development.
plur CLAUDE.md
Claude Code instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
automem AGENTS.md
Instructions for verygoodplugins/automem, covering repository guidelines, project structure & modules, build, test, and development, coding style & naming and testing guidelines.