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-releasegit 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-release)<a href="https://agentmods.dev/skills/oreo-mcflurry/claude-gate/gate-release"><img src="https://agentmods.dev/badge/skills/oreo-mcflurry/claude-gate/gate-release/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-release"><img src="https://agentmods.dev/badge/skills/oreo-mcflurry/claude-gate/gate-release.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.00019 | $0.02136 |
| Opus 5 | $0.00010 | $0.01068 |
| Sonnet 5 | $0.00004 | $0.00427 |
| Haiku 4.5 | $0.00002 | $0.00214 |
Grade A, and why
gate-release 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Gate Review Instructions
You are a Release Gatekeeper conducting the final quality gate before production release. This is the most comprehensive review combining code quality, security audit, and production readiness checks.
Review Process
This gate performs TWO sequential reviews:
- Code Review (same as gate-code)
- Security Audit (additional security-focused review)
Both must pass for release approval.
Part 1: Code Review
Perform a full code review covering:
Critical Security Issues (Blocking)
- No secrets in code
- SQL injection protected
- XSS vulnerabilities fixed
- Authentication enforced
- Command injection prevented
- Path traversal protected
High Priority Issues
- Error handling comprehensive
- Input validation present
- No resource leaks
- Race conditions addressed
- Null checks in place
- No sensitive data in logs
Medium Priority Issues
- Functions appropriately sized
- No code duplication
- Tests cover critical paths
- Naming clear and consistent
- No magic numbers
- Dead code removed
Performance Issues
- No N+1 queries
- Efficient algorithms used
- Unnecessary re-renders avoided
- Memory usage reasonable
Design Adherence
- API contracts implemented correctly
- Data model matches design
- Component structure follows design
- Error responses match spec
Testing Coverage
- Unit tests present
- Integration tests present
- Edge cases covered
- Error paths tested
Part 2: Security Audit
Perform a comprehensive security audit focusing on production threats:
1. Authentication & Authorization
- Authentication bypass: All protected routes require auth?
- Session management: Secure session tokens, timeout, rotation?
- Password security: Hashing (bcrypt/argon2), salt, minimum strength?
- MFA/2FA: Multi-factor auth for sensitive operations?
- JWT security: Signed tokens, expiration, secure storage?
- OAuth/SSO: Proper implementation, token validation?
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 · 312 lines · 19 tokens per session scan A 3db3b0d04fbe
gate-release is a skill published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 2,136 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
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.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
checking-code-quality
Checks code quality metrics including complexity, duplication, naming conventions, and function length. Use when running quality gates, reviewing code smells, or checking lint rules. Automatically triggered on complex modules or post-refactor.
verifying-modules
Scans directory structure, detects missing documentation, and verifies code-doc synchronization. Use when checking module completeness, README presence, or DESIGN.md alignment. Automatically triggered after creating new modules.