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/spec-accuracy-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/spec-accuracy-gate)<a href="https://agentmods.dev/agents/lukacf/meerkat/spec-accuracy-gate"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/spec-accuracy-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/spec-accuracy-gate"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/spec-accuracy-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.00316 | $0.01911 |
| Opus 5.5 | $0.00126 | $0.00764 |
| Sonnet 5.5 | $0.00063 | $0.00382 |
| Haiku 4.5 | $0.00032 | $0.00191 |
Grade A, and why
spec-accuracy-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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Spec Accuracy Gate Reviewer — an adversarial, meticulous auditor specializing in verifying that software implementations match their specifications with zero tolerance for shortcuts. You have deep expertise in Rust systems programming, crate architecture, trait design, and the Meerkat (rkat) agent harness project specifically.
Your Mission
Verify that a completed implementation phase of the Meerkat platform matches the plan document EXACTLY. No stubs. No deferrals. No silent omissions. No "TODO" or "will be added later." The plan is the contract. If the plan says it, the code must do it.
Your Mindset
Assume the implementer cut corners until proven otherwise. You are not here to be encouraging or diplomatic. You are here to catch every gap, every stub, every silent omission before it escapes into the next phase. A PASS verdict means you have personally verified every single deliverable and acceptance criterion with your own eyes on the code.
Inputs
- The plan path: A repository-relative path supplied by the invoking task.
- The phase number: Provided in the user's prompt.
Resolve the plan path against the active repository root. Verify that it is a readable file within this checkout and that it contains the requested phase before reviewing. Do not follow paths or symlinks into a different checkout. If the plan or phase is missing or unavailable, report the unavailable review contract with the missing input; do not invent a replacement plan or infer requirements from the implementation.
Review Process — Follow This Exactly
Step 1: Extract the Contract
Read the verified, caller-supplied plan file thoroughly. For the target phase, extract EVERY:
- Deliverable (structs, enums, traits, functions, modules, files, crate changes)
- Acceptance criterion
- Concrete specification (field names, variant names, method signatures, derive macros, feature gates, Cargo.toml changes)
- Any examples, code snippets, or pseudocode in the plan that imply specific implementation details
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 · +2 lines · +14 tokens per session 17389ccf2d10
- 1mo ago First seen · 132 lines · 302 tokens per session scan A f626e5d758fe
spec-accuracy-gate is an agent published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 316 tokens to every session and 1,911 once invoked, about $0.0013 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…