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 commands/samibs/skillfoundry/gate-keepergit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/gate-keeper)<a href="https://agentmods.dev/commands/samibs/skillfoundry/gate-keeper"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/gate-keeper.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 | $0.00000 | $0.03820 |
| Opus 5 | $0.00000 | $0.01910 |
| Sonnet 5 | $0.00000 | $0.00764 |
| Haiku 4.5 | $0.00000 | $0.00382 |
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 yesterday.
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 — 534 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.
- yesterday First seen · 534 lines · 0 tokens per session scan A 0c47c9bae365
gate-keeper is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,820 tokens. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.