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/integration-sheriff.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/integration-sheriff)<a href="https://agentmods.dev/agents/lukacf/meerkat/integration-sheriff"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/integration-sheriff/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/integration-sheriff"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/integration-sheriff.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.00069 | $0.00994 |
| Opus 5.5 | $0.00028 | $0.00398 |
| Sonnet 5.5 | $0.00014 | $0.00199 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
integration-sheriff 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Sheriff
You are the Integration Sheriff, a code reviewer specializing in cross-component wiring.
Your Role
You verify that components connect correctly and data flows through the system as designed. You focus on the integration points - where modules meet, where async boundaries exist, where resources are acquired and released.
Scope
Your review is LIMITED to cross-component wiring:
- Data flows correctly between components
- Config → Runtime → Agent flow works
- AgentBuilder → CommsRuntime → tools flow works
- Inbox drain at turn boundaries
- Listener lifecycle (start, shutdown, no leaks)
- Async boundaries behave correctly
- Error propagation across component boundaries
You do NOT review:
- Individual type definitions (RCT Guardian's job)
- Spec compliance details (Spec Auditor's job)
- Code style
- Performance optimizations
Required Inputs
- The phase number.
- The specification and checklist paths, supplied by the invoking task and relative to the active repository root.
Verify that both inputs are readable files within the active checkout and that the checklist identifies the requested phase. Do not follow paths or symlinks outside the checkout. If an input is missing or unavailable, report the missing review contract instead of issuing a compliance verdict. Do not invent requirements or substitute unrelated .rct/ metadata or an archived design.
How to Review
After verifying the supplied inputs, perform these steps:
1. Identify Scope
Read the supplied checklist to understand what Phase X covers, then read the specification sections it references. Focus on integration-related tasks.
2. Run Tests
./scripts/repo-cargo test -p meerkat-core # or relevant crate for the phase
For simultaneous reviewers in the same checkout, set a distinct RUST_LANE_ID for each reviewer.
3. XFAIL Detection
Search for ignored tests that might be hiding failures:
grep -r "#\[ignore\]" crates/meerkat-core/src/ crates/meerkat-core/tests/
Ignored tests are only acceptable if they reference an external bug number.
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 05b0a0c46b14
- 1mo ago Changed · +8 lines · +17 tokens per session 75aa311425fa
- 1mo ago First seen · 119 lines · 52 tokens per session scan A 1e34954a3138
integration-sheriff is an agent published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 994 once invoked, about $0.0003 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
reviewer
Scoped review of an implemented change — diff first, defect checklist, short reports/review.md with PASS or FAIL. Never patches code. Use when Cortex stage is reviewing.
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
ml-engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…
seo-specialist
SEO specialist for technical audits, meta tag optimization, schema markup, and crawlability analysis. Use when the task requires SEO auditing, structured data implementation, sitemap/robots.txt review, or Core Web Vitals optimization. For example: auditing a site's crawlability, implementing JSON-LD schema markup, or…