Borrowing it
Nothing to install: this file belongs to DanWahlin/ai-agent-board. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DanWahlin/ai-agent-board/main/.squad/skills/gate-enforcement/SKILL.mdgit clone --depth 1 https://github.com/DanWahlin/ai-agent-boardWrote 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/danwahlin/ai-agent-board/gate-enforcement)<a href="https://agentmods.dev/skills/danwahlin/ai-agent-board/gate-enforcement"><img src="https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/gate-enforcement/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/danwahlin/ai-agent-board/gate-enforcement"><img src="https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/gate-enforcement.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.00017 | $0.00452 |
| Opus 5 | $0.00009 | $0.00226 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
gate-enforcement 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 10d 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.
What it actually says
Context
Use this skill after any task that writes code or changes runtime behavior. Documentation-only Squad state changes only need consistency validation unless they add scripts or app-facing behavior.
Patterns
- Identify the affected surface in
.squad/coverage-matrix.md. - For code-producing work, run the deterministic required gate:
npm run gate:required. - The required gate runs
npm run build:client,npm run build:server, andnpm run test:e2e:required; do not replace it with ad hoc build or E2E commands. - Install the local pre-push hook with
npm run hooks:installso Git uses.githooks/pre-push. - Prefer focused existing tests before broad suites, but required gate evidence must still include
npm run gate:required. - E2E portability/setup problems, including hard-coded Unix paths such as
/tmp/test-repo, are blockers to fix in the test setup before approval; they are not acceptable reasons to defer affected E2E coverage. - Fix-loop ceiling: 3 attempts or 5 minutes on the same failing class, then escalate to Morpheus/Switch.
Examples
- Agent runtime change: Neo owns implementation; Switch requests focused runtime tests plus
npm run gate:required. - Board UI change: Trinity owns implementation; Switch requests focused e2e/component evidence plus
npm run gate:required.
Anti-Patterns
- Do not weaken or skip tests to make a gate pass.
- Do not treat unrelated baseline failures as proof the current change is safe.
- Do not skip affected e2e for convenience, portability, unavailable dev servers, or setup friction; start/fix the required processes or fail the gate.
- Do not replace required e2e evidence with a build-only claim for browser workflow or client-server behavior changes.
- Do not run softer ad hoc E2E commands when
npm run gate:requiredis available.
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.
- 10d ago First seen · 35 lines · 17 tokens per session scan A eb5ceae8b935
gate-enforcement is a skill published in the GitHub repository DanWahlin/ai-agent-board (57 stars, last pushed 15d ago), licensed MIT. It adds 17 tokens to every session and 452 once invoked, about $0.0001 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, mandatory sequential Claude-then-Codex fresh-eyes review/fix loops…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.