Borrowing it
Nothing to install: this file belongs to leancoderkavy/meepo. 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/leancoderkavy/meepo/main/CLAUDE.mdgit clone --depth 1 https://github.com/leancoderkavy/meepoWrote 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/leancoderkavy/meepo/claude-md)<a href="https://agentmods.dev/instructions/leancoderkavy/meepo/claude-md"><img src="https://agentmods.dev/badge/instructions/leancoderkavy/meepo/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.1 | $0.01407 | $0.01407 |
| Opus 5 | $0.00704 | $0.00704 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
meepo 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meepo — Development Guide
Quick Reference
cargo build # Build all crates
cargo test --workspace # Run all 167+ tests
cargo test -p meepo-core # Test a single crate
cargo clippy --workspace # Lint
cargo run -- ask "Hello" # One-shot test (needs ANTHROPIC_API_KEY)
cargo run -- --debug start # Start daemon with debug logging
Architecture
Rust workspace with 7 crates. Dependencies flow downward — meepo-cli depends on everything, leaf crates have no internal dependencies.
| Crate | Purpose |
|---|---|
meepo-cli |
Binary entry point, CLI commands, daemon startup, event loop, config, templates |
meepo-core |
Agent loop, Anthropic API client, 75+ tools, orchestrator, autonomy, platform abstraction |
meepo-channels |
Message bus + channel adapters (Discord, Slack, iMessage, email, Alexa, etc.) |
meepo-knowledge |
SQLite + Tantivy knowledge graph (entities, relationships, full-text search) |
meepo-scheduler |
Watcher runner, 7 watcher types, persistence |
meepo-mcp |
MCP server (STDIO JSON-RPC) and client for external MCP servers |
meepo-a2a |
Google A2A protocol — HTTP server/client for agent-to-agent delegation |
Key Patterns
Tool system: All tools implement ToolHandler trait (name(), description(), input_schema(), execute()). Registered in ToolRegistry at startup. API client runs a tool loop until Claude returns text or hits 10-iteration limit.
Channel adapters: Implement MessageChannel trait (start(), send(), channel_type()). MessageBus splits into receiver + Arc<BusSender> for concurrent use.
Platform abstraction: OS-specific code behind traits in meepo-core::platform (EmailProvider, CalendarProvider, BrowserProvider, etc.). Selected at compile time via #[cfg(target_os)]. Factory functions return Box<dyn Trait>.
Secrets: API keys use ${ENV_VAR} syntax in TOML config, expanded at load time via an allowlist. Structs holding secrets get custom Debug impls (not #[derive(Debug)]). Never hardcode secrets.
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.
- 7d ago First seen · 95 lines · 1,407 tokens per session scan A f3935fd91a0e
meepo CLAUDE.md is an instructions file published in the GitHub repository leancoderkavy/meepo (3 stars, last pushed 6mo ago), licensed MIT. It adds 1,407 tokens to every session, about $0.0070 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
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.
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.
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).
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.