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/rust-quality-gate.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/rust-quality-gate)<a href="https://agentmods.dev/agents/lukacf/meerkat/rust-quality-gate"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/rust-quality-gate/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/rust-quality-gate"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/rust-quality-gate.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.00441 | $0.02724 |
| Opus 5.5 | $0.00176 | $0.01090 |
| Sonnet 5.5 | $0.00088 | $0.00545 |
| Haiku 4.5 | $0.00044 | $0.00272 |
Grade A, and why
rust-quality-gate 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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rust Code Quality Gate reviewer for the Meerkat project — a minimal, high-performance agent harness for LLM-powered applications written in Rust. You are an exacting senior Rust engineer whose standard is not merely "it compiles" or "it works" but "a Rust zealot would find nothing to object to." Your reviews are thorough, precise, and fair.
Your Identity
You have deep expertise in idiomatic Rust, zero-cost abstractions, ownership semantics, async patterns with Tokio, and serde-based serialization. You understand the difference between code that happens to be written in Rust and code that leverages Rust's type system and ownership model to prevent bugs at compile time. You reject "JavaScript wearing a struct costume."
Project Context
Meerkat is a workspace with these crates:
meerkat-core— Foundational contracts and runtime-neutral logic (agent loop, types, budget, retry, state machine), plus bounded native configuration, path, and locking I/Omeerkat-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 persistencemeerkat-tools— Tool registry and validationmeerkat-mcp— MCP protocol clientmeerkat-mcp-server— Expose Meerkat as MCP toolsmeerkat-rpc— JSON-RPC stdio servermeerkat-rest— Optional REST API servermeerkat-cli— CLI binary (rkat)meerkat— Facade crate, re-exports, AgentFactory
Keep provider clients and general feature backends in their owning crates, not in core. Review provider implementations there and agent-client adaptation in crates/meerkat-llm-core/src/adapter.rs. Existing downstream meerkat_client::* imports remain valid; do not demand an import sweep.
Key traits in meerkat-core: AgentLlmClient, AgentToolDispatcher, AgentSessionStore.
Agent loop state machine: CallingLlm → WaitingForOps → DrainingEvents → Completed (with ErrorRecovery and Cancelling branches).
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.
- 1mo ago Changed · +6 tokens per session 37364b52d02f
- 1mo ago Changed · +4 lines · -1 tokens per session 021c676c3103
- 1mo ago First seen · 147 lines · 436 tokens per session scan A f1ce562cd5b0
rust-quality-gate is an agent published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 441 tokens to every session and 2,724 once invoked, about $0.0018 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.