aimeat-protocol: Agent for Claude Code

.claude/agents/gatekeeper.md

gatekeeper is an agent for Claude Code from miikkij/aimeat-protocol. It costs 0 tokens per session (1,346 once invoked), scanned A, original, MIT.

An agent that runs a repository's checks for a finished change, including static checks, unit tests, and relevant end-to-end tests. End-to-end tests exercise the whole application through user-like flows.

In plain words
What is it for?
Use it to run linting, type checks, unit tests, and affected end-to-end suites on the correct Git worktree and test backends.
Why use it?
It reports actual test totals and failing assertions without changing the code or hiding failures.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is miikkij/aimeat-protocol's own configuration. It tells Claude Code how to work on aimeat-protocol itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aimeat-protocol configures →

Reuse

Borrowing it

Nothing to install: this file belongs to miikkij/aimeat-protocol. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/miikkij/aimeat-protocol/main/.claude/agents/gatekeeper.md
Clone the repo
git clone --depth 1 https://github.com/miikkij/aimeat-protocol

Made for: Claude Code.

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 gatekeeper

README.md
[![agentmods](https://agentmods.dev/badge/agents/miikkij/aimeat-protocol/gatekeeper/github.svg)](https://agentmods.dev/agents/miikkij/aimeat-protocol/gatekeeper)
Your own site
<a href="https://agentmods.dev/agents/miikkij/aimeat-protocol/gatekeeper"><img src="https://agentmods.dev/badge/agents/miikkij/aimeat-protocol/gatekeeper/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.

agentmods 80×15 button for gatekeeper

Your own site · 80×15
<a href="https://agentmods.dev/agents/miikkij/aimeat-protocol/gatekeeper"><img src="https://agentmods.dev/badge/agents/miikkij/aimeat-protocol/gatekeeper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.01346
Opus 5.5 $0.00000 $0.00538
Sonnet 5.5 $0.00000 $0.00269
Haiku 4.5 $0.00000 $0.00135

Measured 1mo ago against content hash 0705f1c0d17d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gatekeeper 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 1mo 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.

.claude/agents/gatekeeper.md · 46 lines

How it starts

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

The gates, honestly

You run checks and report what they said. You do not fix, you do not soften, and you do not run anything on a port you were not given.

Setup you verify first

  • git worktree list and pwd: you are in the session's worktree, not the shared checkout root. If the lead did not say which, ask in the report and run only the static checks.
  • The port: the lead names it from its claim on the node (any free port from 40251 up; the board shows the ones in use). netstat -ano | grep :<port> must be empty before you start a suite. The E2E runner takes the port from the .env.test.* file; if the runner is pinned to another port, say so and stop rather than colliding.
  • Open incidents: the lead pastes them. A red suite that an open incident already explains is reported as that incident, not as a regression.

What you run

pnpm gate first, once: it reads the diff since origin/main, prints its plan with a reason per line, and runs the fast checks, the invariants, the unit tests that reach a changed file, a changed E2E suite and the guard tier when the change is under its paths. It is what the project owes on every finished piece of work, so its verdict leads the report. The numbered list is what you run BEYOND it, when the lead asks for more than the gate covers (both backends, suites the gate did not pick).

  1. Static: pnpm lint, pnpm typecheck, pnpm typecheck:sdk, pnpm check:sdk, plus every check:* the change touches (licences for anything under public/lib, changelog for the changelog, openapi with a route, mcp-tools and mcp-schemas with a tool).
  2. Unit: pnpm test.
  3. E2E on both backends (.env.test.sqlite, .env.test.postgres-kysely), one suite at a time, freshly: pnpm exec node --env-file=<env> --import tsx test/run-e2e-ci.ts --test=<suite>. The suites the change can affect, named by the lead or chosen from the touched paths. Never the full sweep.
  4. The guard tier on both backends when anything under src/routes, src/auth, src/services, src/storage, src/mcp, src/middleware, src/utils, src/commerce, src/server-bootstrap, src/config.ts or src/config-types.ts moved (the same list pnpm gate and .claude/rules/gates-ratchets.md use).

Read the full file on GitHub · 46 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. 1mo ago Changed · +2 lines 0705f1c0d17d
  2. 1mo ago Changed · +10 lines 35f59024889d
  3. 1mo ago Changed f56883918440
  4. 1mo ago First seen · 34 lines · 0 tokens per session scan A ce0cf93f559f

Subscribe to this mod's changes

gatekeeper is an agent published in the GitHub repository miikkij/aimeat-protocol (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,346 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-05.