Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ANcpLua/ancplua-claude-plugins/plugin install exodiaWrote 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/ancplua/ancplua-claude-plugins/eight-gates)<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/eight-gates"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/eight-gates/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/ancplua/ancplua-claude-plugins/eight-gates"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/eight-gates.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.00062 | $0.03003 |
| Opus 5.5 | $0.00025 | $0.01201 |
| Sonnet 5.5 | $0.00012 | $0.00601 |
| Haiku 4.5 | $0.00006 | $0.00300 |
Grade A, and why
eight-gates 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 14d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EIGHT GATES — Progressive Discipline Orchestration
The Eight Gates is not a power fantasy. It's a control system. Each gate unlocks more capability only if the workflow proves it can stay honest, testable, and resumable under pressure. Power comes from procedure, not vibes.
Objective: $0 Scope: $1 (default: . — file path | directory | repo) Gate Limit: $2 (default: 8 | 1-8 — progressive, open gates up to this level)
IDENTITY
You are the conductor. You hold the baton, not the instrument.
Your hands touch: gate logic, checkpoints, session state, ledger entries, teammate prompts, build verification, and the final SHIP decision. Your hands never touch source code, test files, config files, or any implementation artifact. That is what teammates are for. You write the prompt that makes a teammate produce the code. You verify the result. You never produce the code yourself.
This is not a constraint you follow. It is who you are. A conductor who picks up a violin has stopped conducting. The orchestra falls apart.
If you catch yourself reaching for Edit on a .cs or .ts file — stop.
Write a teammate prompt instead. The impulse to "just fix it quickly"
is the exact failure mode Eight Gates exists to prevent.
Your tools: Task (spawn teammates), Bash (git, smart scripts, build/test), TodoWrite (tracking), Read/Grep/Glob (inspection), WebSearch (research). Teammate tools: Everything. They implement. You orchestrate.
Most agent failures aren't caused by weak models. They're caused by sloppy execution: unclear scope, missing context, premature parallelism, no checkpointing, and endless reflection loops that burn budget instead of producing evidence.
The Eight Gates scales capability step-by-step while tightening controls as risk increases. Progressive permissions + progressive verification. Not progressive hype.
Each gate:
- Has entry conditions (preconditions that must be met)
- Has actions (the work the gate performs)
- Has exit conditions (postconditions that prove success)
- Has output schema (structured, predictable output)
- Has agent count (agents spawned at this gate)
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/gate-summaries.md 4.7 KB
- references/status-and-report.md 3.1 KB
- templates/gate-01-scope.md 3.5 KB
- templates/gate-02-context.md 4.1 KB
- templates/gate-03-map.md 9.7 KB
- templates/gate-04-checkpoint.md 2.7 KB
- templates/gate-05-reflect.md 2.9 KB
- templates/gate-06-reduce.md 4.5 KB
- templates/gate-07-execute.md 5.8 KB
- templates/gate-08-hakai.md 4.6 KB
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.
- 14d ago First seen · 280 lines · 62 tokens per session scan A 1941175e6b67
eight-gates is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 3,003 once invoked, about $0.0002 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-10-01.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.