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 Arch1eSUN/Arcgentic --skill verify-gatesgit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/verify-gates)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/verify-gates"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/verify-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/arch1esun/arcgentic/verify-gates"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/verify-gates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.00627 |
| Opus 5 | $0.00037 | $0.00313 |
| Sonnet 5 | $0.00015 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
verify-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 9d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify gates
What this skill does
arcgentic's state machine has 4 gates (MVP):
| Gate | Transition | Verifies |
|---|---|---|
handoff-doc-gate.sh |
planning → awaiting_dev_start |
handoff doc exists + has all required sections |
round-commit-chain-gate.sh |
dev_in_progress → awaiting_audit (also fix_in_progress → awaiting_audit) |
dev_commits count ≥ expected + every SHA resolves in git |
verdict-fact-table-gate.sh |
`audit_in_progress → passed | needs_fix` |
transition.sh runs the required gate automatically. This skill is for the orchestrator (or human) when they want to pre-verify before attempting the transition.
When to invoke this skill
- About to ask a sub-agent to attempt a state transition → invoke this skill first, run the gate, fix any failures, then transition
- A transition failed and the orchestrator wants to know WHY → invoke this skill, run the relevant gate, read the failure reason
- Setting up a new gate for a project-specific transition → this skill's
references/gate-script-catalog.mdshows the gate-script shape
Gate script contract
Every gate script:
- Takes
--state-file PATHas its only argument - Reads state.yaml + does whatever check it does
- Exits 0 on PASS, 1 on FAIL
- Prints PASS line to stdout, FAIL reason to stderr
This contract means gates are composable. You can chain them. You can write project-specific ones in your own <project>/.agentic-rounds/gates/ and reference them in state.yaml's states.<state>.gate field.
Run a gate manually
bash $PLUGIN_ROOT/scripts/gates/handoff-doc-gate.sh \
--state-file <project>/.agentic-rounds/state.yaml
echo "exit: $?"
Adding a project-specific gate
- Write
<project>/.agentic-rounds/gates/your-gate.shfollowing the contract above - Edit state.yaml: set
states.<source-state>.gatetoyour-gate.sh - Run
transition.sh --gates-dir <project>/.agentic-rounds/gates ...(override built-in gates dir)
What ships with it
1 file 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.
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.
- 9d ago First seen · 53 lines · 75 tokens per session scan A 6a9288ebe315
verify-gates is a skill published in the GitHub repository Arch1eSUN/Arcgentic (293 stars, last pushed 27d ago), licensed MIT. It adds 75 tokens to every session and 627 once invoked, about $0.0004 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.
Other skills, from other repositories
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
refactor
Refactor existing code by extracting helpers, splitting files, removing duplication, or untangling dependencies. Supports resumable and batch runs. Use for structural changes that preserve behavior; use zuvo:build for new features.
ccc-testing
Default isolation: worktree — test dispatches run in an isolated worktree to avoid polluting the working tree.
parallel-lifecycle
Run and CDP-test a feature inside its own git worktree without colliding with other parallel coding sessions. Use whenever you are testing a feature locally in a worktree, running Playwright/CDP against your own app, or running two or more agent sessions in parallel that each need a dev server and a browser. Trigger…
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.