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 renezander030/skillgate --skill skillgategit clone --depth 1 https://github.com/renezander030/skillgateWrote 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/renezander030/skillgate/skillgate)<a href="https://agentmods.dev/skills/renezander030/skillgate/skillgate"><img src="https://agentmods.dev/badge/skills/renezander030/skillgate/skillgate/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/renezander030/skillgate/skillgate"><img src="https://agentmods.dev/badge/skills/renezander030/skillgate/skillgate.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.00119 | $0.01972 |
| Opus 5.5 | $0.00048 | $0.00789 |
| Sonnet 5.5 | $0.00024 | $0.00394 |
| Haiku 4.5 | $0.00012 | $0.00197 |
Grade A, and why
skillgate 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 12d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skillgate
Deterministic gates that decide when work is actually finished. No model judges the
result: gates are declared as data in .skillgate/done.yaml and evaluated by running
commands and inspecting files. Exit codes are the contract — check exits 1 on failure,
gate exits 2 to block a command.
Every command below runs with no install: npx @reneza/skillgate <command>. In a project
that has it as a devDependency, drop the npx @reneza/ prefix.
Start here
npx @reneza/skillgate audit # read-only, no config: what would let a patch through unfinished
audit needs no .skillgate/done.yaml. It reports against built-in defaults and is the
right first command in an unfamiliar repo. Report its output to the user before changing
anything.
Wire the gate in
npx @reneza/skillgate init # write a starter .skillgate/done.yaml
npx @reneza/skillgate install claude-code # fail-closed PreToolUse hook in .claude/settings.json
npx @reneza/skillgate install claude-code --stop # also refuse to end the turn while gates fail
npx @reneza/skillgate install codex # or gemini-cli, cursor: the same gate in each agent's hook
npx @reneza/skillgate install all # every agent hook + opencode + github-actions + pre-commit
npx @reneza/skillgate doctor all # policy + integration health check
install is idempotent, pins generated npm commands to the installed version, and writes
hooks that block when the gate itself cannot run. Prefer it over hand-editing agent
settings. If doctor says a hook "fails open", re-run install for that target.
Layers are not equal, and the user should know which one they picked: a PreToolUse hook is
fast feedback inside the loop and the agent's own environment can undo it; pre-commit is
bypassable with --no-verify; CI with branch protection is the layer that actually holds.
Recommend CI as the backstop whenever the repo is shared.
Run the gate
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.
- 12d ago Changed · +4 lines e5f78e9715be
- 26d ago Changed · +30 lines c99c90bbfef8
- 1mo ago First seen · 108 lines · 119 tokens per session scan A 8c506dafd182
skillgate is a skill published in the GitHub repository renezander030/skillgate (8 stars, last pushed 4d ago), licensed MIT. It adds 119 tokens to every session and 1,972 once invoked, about $0.0005 per session on Opus 5.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-09-19.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.
e2e-testing
Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.