gate-check

gate-check is a skill for Claude Code, Codex from jongwony/epistemic-protocols. It costs 40 tokens per session (10,715 once invoked), scanned A, original, MIT.

A review of a set of choices by an independent advisor, followed by checks of the reasons supporting those choices.

In plain words
What is it for?
Use it to assess a draft decision gate and verify that each option has a defensible basis before presenting it.
Why use it?
It helps detect when proposed options are incomplete, malformed, or based on the wrong decision criteria.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also runs codex exec. Also seen: mentions Codex.

Part of the epistemic-cooperative plugin — 13 skills shipped together

Install

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.

agentmods
npx agentmods add skills/jongwony/epistemic-protocols/gate-check
Any agent
npx skills add jongwony/epistemic-protocols --skill gate-check
Clone the repo
git clone --depth 1 https://github.com/jongwony/epistemic-protocols

Made for: Claude Code, Codex.

Or install epistemic-cooperative, the plugin that ships this one along with the rest of its 13 skills.

Wrote 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.

agentmods badge for gate-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/jongwony/epistemic-protocols/gate-check.svg)](https://agentmods.dev/skills/jongwony/epistemic-protocols/gate-check)
Your own site
<a href="https://agentmods.dev/skills/jongwony/epistemic-protocols/gate-check"><img src="https://agentmods.dev/badge/skills/jongwony/epistemic-protocols/gate-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,715 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.10715
Opus 5 $0.00020 $0.05358
Sonnet 5 $0.00008 $0.02143
Haiku 4.5 $0.00004 $0.01072

Measured 6d ago against content hash 107c1781ee66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gate-check 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 6d 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.

epistemic-cooperative/skills/gate-check/SKILL.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Gate Check

An option set is normally judged by whoever drafted it. That is the one judgment the drafter cannot make well: the options inherit the frame they were drafted from, so an option set standing on the wrong axis looks complete from inside. This skill puts an independent adjudicator on the option set itself — not on the work the gate is about — and then checks the adjudicator's reasoning against the substrate before either reaches you.

The check separates two things that usually collapse into one: who wrote the options and who says they are worth asking. Everything below exists to keep those apart, including from itself.

Caller Signature

/gate-check [gate?] [advisor?]

gate    : (implicit) | explicit draft   -- optional; defaults to the gate drafted in the current turn
advisor : { codex }                     -- optional; the independent adjudicator behind the
                                        --   (gate question, frozen option set, settled
                                        --    constraints, pointers)
                                        --   → { axis reading, falsifier, a ground cited for every
                                        --      conclusion asserted, and either a verdict — with
                                        --      what a collapse reduces to, or what axis a
                                        --      malformed relocates onto — or, where none of the
                                        --      three fits, the members it could not clear with
                                        --      the repairs available and what each changes }
                                        --      interface

The advisor is a parameter, not the identity. Any adjudicator satisfying that interface can drive the check, provided it is a genuinely separate reasoner — a second pass by the drafting agent does not satisfy it, because the independence is the whole mechanism.

Pipeline Overview

/gate-check [gate?] [advisor?]
  Phase 0 : screen + freeze     -- eligible gate? → freeze the option set verbatim, capture a substrate anchor
  Phase 1 : launch ∥ precommit  -- dispatch to the advisor (background), then record the expected
                                   controlling sources and verification criteria BEFORE any advisor
                                   output is visible
  Phase 2 : verify              -- collect the advisor's own words; check each cited ground against
                                   the substrate; check whether its stated falsifier could have
                                   defeated the reading and whether it is there
  Phase 3 : dispose             -- genuine | collapse | malformed | indeterminate | failed
  Phase 4 : synthesize          -- on a settled repair: rebuild the option set under the synthesis guards,
                                   then one external recheck, bounded
  present                       -- three vantage points always; ground-by-ground detail folds to one line
  observer                      -- armed for the session; every cycle converges or fails explicitly

Read the full file on GitHub · 259 lines

Changes

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.

  1. 6d ago First seen · 259 lines · 40 tokens per session scan A 107c1781ee66

Subscribe to this mod's changes

gate-check is a skill published in the GitHub repository jongwony/epistemic-protocols (160 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 10,715 once invoked, about $0.0002 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.