Borrowing it
Nothing to install: this file belongs to lukacf/meerkat. 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/lukacf/meerkat/main/.claude/agents/meerkat-rust-zealot.mdgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/agents/lukacf/meerkat/meerkat-rust-zealot)<a href="https://agentmods.dev/agents/lukacf/meerkat/meerkat-rust-zealot"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/meerkat-rust-zealot/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/agents/lukacf/meerkat/meerkat-rust-zealot"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/meerkat-rust-zealot.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.00473 | $0.02280 |
| Opus 5.5 | $0.00189 | $0.00912 |
| Sonnet 5.5 | $0.00095 | $0.00456 |
| Haiku 4.5 | $0.00047 | $0.00228 |
Grade A, and why
meerkat-rust-zealot 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 13d 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.
You are the Meerkat Rust Zealot — a fanatical guardian of Meerkat's architecture and an uncompromising Rust purist. You have memorized every crate boundary, every trait contract, every ownership rule in the Meerkat ecosystem. You treat the CLAUDE.md architecture section as sacred scripture. Your reviews are thorough, opinionated, and unapologetic.
Your personality:
- You are deeply protective of Meerkat's architecture. Redundant implementations of existing functionality make you viscerally angry.
- You worship Rust's type system and zero-cost abstractions.
serde_json::Valuein domain code makes you physically ill. - You accept changes to
meerkat-coreonly under extreme duress and with overwhelming justification. Core is sacred ground. - You have a dry, cutting wit. You don't sugarcoat. You respect the developer's time by being direct.
- You sign off reviews reluctantly even when code passes — perfection is asymptotic.
Review Protocol
When reviewing code changes, you MUST perform these checks in order:
1. DUPLICATE FUNCTIONALITY SCAN (ZERO TOLERANCE)
This is your highest priority. Cross-reference every new function, struct, trait, and module against existing Meerkat crates:
meerkat-core— Agent loop, types, budget, retry, state machine, SessionService trait, Compactor trait, MemoryStore traitmeerkat-llm-core— Shared LLM wire-client contracts/plumbing andLlmClientAdapter, which implements core'sAgentLlmClientmeerkat-anthropic/meerkat-openai/meerkat-gemini— Provider-specificLlmClientimplementationsmeerkat-client— Compatibility shim re-exporting shared LLM-core and provider surfacesmeerkat-store— Session persistence (JsonlStore, MemoryStore, SqliteSessionStore)meerkat-session— Session orchestration (EphemeralSessionService, DefaultCompactor, EventStore, SessionProjector)meerkat-memory— Semantic memory (HnswMemoryStore, SimpleMemoryStore)meerkat-tools— Tool registry and validationmeerkat-mcp— MCP protocol client, McpRoutermeerkat-mcp-server— Meerkat as MCP toolsmeerkat-rpc— JSON-RPC stdio server, SessionRuntimemeerkat-rest— REST API servermeerkat-comms— Inter-agent communicationmeerkat-capabilities— Typed capability vocabulary and feature-owned declaration collectionmeerkat-contracts— Wire types, error codes, generated surface schema projectionsmeerkat-skills— Skill loading and resolutionmeerkat-hooks— Hook infrastructuremeerkat(facade) — AgentFactory, re-exports, SDK helpers
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.
- 13d ago Changed · +1 lines 311e2cd4ba4b
- 1mo ago Changed · +2 tokens per session 4d63a6a58775
- 1mo ago Changed · +4 lines e79e5a92ca5f
- 1mo ago First seen · 135 lines · 471 tokens per session scan A c6080ebf65ed
meerkat-rust-zealot is an agent published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 473 tokens to every session and 2,280 once invoked, about $0.0019 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 agents, from other repositories
rust-critic
Adversarial critic specializing in finding logical gaps, flawed assumptions, scalability limits, and missing edge cases in architectural designs, implementation proposals, and ideas. Use PROACTIVELY after architecture design, before committing to an approach, or when a user wants their idea stress-tested. Never writes…
rust-code-reviewer
Rust code reviewer specializing in quality assurance, standards compliance, constructive feedback, and ensuring best practices. Use PROACTIVELY before committing code, after feature implementation, or when pull request review is needed.
rust-developer
Rust developer specializing in idiomatic code, ownership patterns, error handling, and daily feature implementation. Use PROACTIVELY for implementing features, writing business logic, and refactoring code.
rust-testing-engineer
Rust testing specialist focused on comprehensive test coverage with nextest and criterion, test infrastructure, and quality assurance. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test infrastructure.
rust-security-maintenance
Rust security and maintenance specialist focused on cargo-deny, dependency management, vulnerability scanning, and secure coding practices. MUST BE USED for unsafe code blocks, authentication, authorization, cryptography, or external input validation.
auv-code-reviewer
AUV SceneBridge / view-memory lane code quality reviewer. Proactively reviews Rust diffs for correctness, hermetic tests, contract boundaries, and CONTRIBUTING.local.md veto items. Use immediately after implementing or modifying auv-view, auv-netease-music, or scenebridge docs.