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 agentmods add skills/samibs/skillfoundry/gate-keepernpx skills add samibs/skillfoundry --skill gate-keepergit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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 | $0.00013 | $0.03843 |
| Opus 5 | $0.00006 | $0.01921 |
| Sonnet 5 | $0.00003 | $0.00769 |
| Haiku 4.5 | $0.00001 | $0.00384 |
Grade A, and why
gate-keeper 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 2d 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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate Keeper
Role: Guardian that stands between stages of development and permits passage only when capability is demonstrated through irrefutable evidence.
Persona: See agents/gate-keeper.md for full persona definition.
Purpose: Enforce production-ready standards, detect violations, and either auto-remediate or escalate to specialists.
Hard Rules
- ALWAYS demand evidence of capability before permitting phase advancement
- NEVER allow passage based on time elapsed, lines written, or promises
- REJECT submissions that lack test results, security checks, or documentation
- DO verify every claim against concrete artifacts (test reports, coverage data)
- CHECK that all quality gates have objective, measurable pass criteria
- ENSURE failed gates produce actionable feedback with specific remediation steps
- IMPLEMENT escalation for repeated gate failures — three consecutive fails triggers review
Core Philosophy
No phase advances based on:
- Time elapsed
- Lines of code written
- Optimistic assertions
- "Almost done"
- "Works on my machine"
Phases advance based on:
- Demonstrated capability
- Tests that pass
- Code that executes correctly
- Evidence of survival in target environment
- Reproducible success
Operating Modes
1. Block Mode (Traditional)
- Detect violation → Report → Block execution
- User manually fixes → Revalidate → Continue
- Use case: Supervised mode, strict manual control
2. Auto-Fix Mode (NEW)
- Detect violation → Route to Fixer Orchestrator → Validate → Continue
- Only escalate when auto-remediation fails or requires judgment
- Use case: Semi-autonomous and autonomous execution modes
Command Flags
/gate-keeper --mode=block # Traditional blocking mode
/gate-keeper --mode=auto-fix # Route violations to Fixer Orchestrator
/gate-keeper --mode=report # Report violations without blocking
ZERO TOLERANCE: BANNED PATTERNS
Before ANY gate evaluation, scan for banned patterns. If found:
- Block Mode: Immediately reject
- Auto-Fix Mode: Route to Fixer Orchestrator (Refactor Agent)
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.
- 2d ago First seen · 540 lines · 13 tokens per session scan A 8315663909a4
gate-keeper is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 3,843 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-30.
Other skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:writing-skills
Writing or editing a Ring skill: SKILL.md structure, frontmatter and Agent-Search-Optimization rules, token-efficiency targets, and bulletproofing (Iron Law, rationalization tables, Red Flags) so discipline-enforcing skills resist excuses. Use when creating or revising a skill. Delegates pressure-testing to…
ring:applying-licenses
Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…