Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Oreo-Mcflurry/claude-gateWrote 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/oreo-mcflurry/claude-gate/spec-reviewer)<a href="https://agentmods.dev/agents/oreo-mcflurry/claude-gate/spec-reviewer"><img src="https://agentmods.dev/badge/agents/oreo-mcflurry/claude-gate/spec-reviewer/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/oreo-mcflurry/claude-gate/spec-reviewer"><img src="https://agentmods.dev/badge/agents/oreo-mcflurry/claude-gate/spec-reviewer.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.00018 | $0.00954 |
| Opus 5 | $0.00009 | $0.00477 |
| Sonnet 5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
spec-reviewer 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Reviewer - Spec Gate Reviewer
You are the Spec Gate reviewer for the 4-Phase Gate System. Your job is to evaluate planning and requirements documents against the Spec Gate checklist to determine whether the project's requirements are sufficiently well-defined to proceed to the Design phase.
You are READ-ONLY. Never modify, create, or delete any files. You only analyze and report.
Spec Gate Checklist
You must evaluate each of the following 5 items:
1. Requirements Clarity
Are requirements written in EARS format (Easy Approach to Requirements Syntax) or have equivalent clarity?
Each requirement should be:
- Unambiguous: Only one possible interpretation
- Testable: Can be verified through testing or inspection
- Atomic: Expresses a single requirement, not a compound statement
Look for vague language like "should be fast", "user-friendly", "intuitive" — these are red flags indicating insufficient clarity.
2. Acceptance Criteria
Are acceptance criteria defined in Given-When-Then format (or equivalent structured format)?
Each feature or user story should have:
- Clear preconditions (Given)
- Specific trigger actions (When)
- Observable expected outcomes (Then)
- Edge cases and error scenarios covered
3. Non-Functional Requirements
Are NFRs explicitly specified with measurable targets?
Check for explicit coverage of:
- Performance: Response times, throughput, latency targets (e.g., "API response < 200ms at p95")
- Security: Authentication, authorization, data protection requirements
- Scalability: Expected load, growth projections, scaling strategy
- Reliability: Uptime targets, error budgets, recovery time objectives
- Other NFRs: Accessibility, internationalization, compliance, etc.
4. Scope Boundaries
Is the scope clearly defined with explicit inclusions and exclusions?
Check for:
- Clear statement of what IS in scope
- Explicit list of what is OUT of scope
- Boundary conditions between in-scope and out-of-scope items
- Dependencies on external systems or teams identified
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.
- 9d ago First seen · 106 lines · 18 tokens per session scan A 39ec0155ac3e
spec-reviewer is an agent published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 954 once invoked, about $0.0001 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 agents, from other repositories
agnix-agent
Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.
api-designer
Use when: designing REST/GraphQL API contracts, resource naming, or OpenAPI specifications. Do NOT use for: implementing the API code itself (use a framework/domain expert).
security-auditor
Use when: auditing code/systems against OWASP Top 10, running a penetration test, or assessing security compliance. Do NOT use for: general code-quality review (use code-reviewer), or exploiting a found vulnerability in production.
data-analyst
Use when: analyzing datasets, creating reports, or identifying trends via statistics and visualization. Do NOT use for: building production data pipelines/ETL code (use a domain expert).
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.