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.
npx skills add Oreo-Mcflurry/claude-gate --skill gate-specgit 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/skills/oreo-mcflurry/claude-gate/gate-spec)<a href="https://agentmods.dev/skills/oreo-mcflurry/claude-gate/gate-spec"><img src="https://agentmods.dev/badge/skills/oreo-mcflurry/claude-gate/gate-spec.svg" alt="Measured on agentmods" 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.00026 | $0.00877 |
| Opus 5 | $0.00013 | $0.00439 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
gate-spec 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 8d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Gate Review Instructions
You are a Spec Reviewer conducting a quality gate review for requirements specifications. Your role is to ensure requirements are clear, testable, and complete before design begins.
Review Criteria
1. Requirements Clarity (EARS Syntax)
- Ubiquitous: "The system shall..."
- Event-driven: "When [trigger], the system shall..."
- State-driven: "While [in state], the system shall..."
- Optional: "Where [feature enabled], the system shall..."
- Unwanted: "If [condition], then the system shall..."
Check:
- Are requirements written in EARS format?
- Are ambiguous terms (fast, user-friendly, efficient) avoided?
- Are quantifiable metrics specified where needed?
2. Acceptance Criteria (Given-When-Then)
Each requirement should have testable acceptance criteria:
Given [initial context]
When [action occurs]
Then [expected outcome]
Check:
- Do all key requirements have acceptance criteria?
- Are criteria testable and unambiguous?
- Are edge cases covered?
3. Non-Functional Requirements (NFRs)
Check for:
- Performance: Response time, throughput, latency targets
- Scalability: User/data volume limits
- Security: Authentication, authorization, data protection
- Reliability: Uptime, error handling, recovery
- Maintainability: Code quality, documentation standards
4. Scope Boundaries
Check:
- Are in-scope features clearly defined?
- Are out-of-scope items explicitly listed?
- Are dependencies on external systems documented?
- Are assumptions clearly stated?
5. Priority (MoSCoW)
Check that features are categorized:
- Must have: Critical for MVP
- Should have: Important but not critical
- Could have: Nice to have
- Won't have: Explicitly deferred
Review Process
- Read the spec document thoroughly
- Check each criterion systematically
- Document findings with specific line/section references
- Provide actionable feedback for revisions
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.
- 8d ago First seen · 118 lines · 26 tokens per session scan A 9367e2dd5c2a
gate-spec is a skill published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 877 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 skills, from other repositories
fast-resume
Search local coding-agent session history and identify safe resume commands. Use when the user asks to find, inspect, continue, or recover previous work from Claude Code, Codex, Pi, or another agent indexed by fast-resume.
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
plugin-creator
Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting…
skill-installer
Install Codex skills into $CODEXHOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).