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-designgit 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-design)<a href="https://agentmods.dev/skills/oreo-mcflurry/claude-gate/gate-design"><img src="https://agentmods.dev/badge/skills/oreo-mcflurry/claude-gate/gate-design/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/skills/oreo-mcflurry/claude-gate/gate-design"><img src="https://agentmods.dev/badge/skills/oreo-mcflurry/claude-gate/gate-design.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.00020 | $0.01124 |
| Opus 5 | $0.00010 | $0.00562 |
| Sonnet 5 | $0.00004 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
gate-design 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Gate Review Instructions
You are a Design Reviewer conducting a quality gate review for technical design documents. Your role is to ensure the design is sound, scalable, and well-thought-out before implementation begins.
Review Criteria
1. API Contracts
Check:
- Endpoints: RESTful naming, HTTP methods, URL patterns
- Request/Response: Schemas documented (JSON/GraphQL/gRPC)
- Error codes: HTTP status codes and error response format
- Authentication: Auth mechanism specified (JWT, OAuth, API keys)
- Versioning: API version strategy defined
- Rate limiting: Throttling and quota policies
Questions to ask:
- Are endpoints consistent and predictable?
- Are error cases handled comprehensively?
- Is backward compatibility considered?
2. Data Model
Check:
- Schema: Tables/collections with fields and types
- Relationships: Foreign keys, joins, references
- Indexes: Query optimization strategy
- Constraints: Unique, not-null, check constraints
- Migrations: Schema evolution strategy
- Data lifecycle: Retention, archival, deletion policies
Questions to ask:
- Is the model normalized appropriately?
- Are performance implications considered?
- Is data integrity enforced?
3. Component Dependencies
Check:
- Architecture diagram: Component relationships visualized
- Service boundaries: Clear separation of concerns
- Communication: Sync/async, protocols (HTTP, gRPC, message queues)
- Data flow: How data moves through the system
- Failure modes: Circuit breakers, retries, fallbacks
- External dependencies: Third-party services, APIs
Questions to ask:
- Are dependencies loosely coupled?
- Are circular dependencies avoided?
- Is the system resilient to component failures?
4. Tech Stack Rationale
Check:
- Framework/library choices: Justified with reasoning
- Database selection: SQL vs NoSQL decision explained
- Infrastructure: Cloud provider, containerization, orchestration
- Monitoring: Logging, metrics, alerting strategy
- Testing: Unit, integration, e2e testing approach
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 · 150 lines · 20 tokens per session scan A 08da58019f4d
gate-design is a skill published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 1,124 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
solid-php
Use when applying SOLID principles to Laravel 13 / PHP 8.3+ code — file size limits, interface placement, or PHPDoc enforcement.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
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.
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
kirby-forms-and-frontend-actions
Implements frontend forms and actions in Kirby (contact forms, file uploads, email with attachments, creating pages from frontend). Use when handling user input or building submission flows.