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 kensaurus/cursor-kenji --skill audit-gate-logicgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-gate-logic)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-gate-logic"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-gate-logic/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/kensaurus/cursor-kenji/audit-gate-logic"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-gate-logic.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.00060 | $0.02642 |
| Opus 5.5 | $0.00024 | $0.01057 |
| Sonnet 5.5 | $0.00012 | $0.00528 |
| Haiku 4.5 | $0.00006 | $0.00264 |
Grade A, and why
audit-gate-logic 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-gate-logic — Does the gate actually stop what it claims?
Degree of freedom: MIXED — Phases 0–2.5 [HIGH freedom]; Phase 3
history/probe [LOW freedom — run exactly] (no scratch branch unless asked).
Read-only. audit-cicd asks "is the pipeline fast, cheap, and safe to run."
This asks "does the gate stop what it claims to stop." A green check is a
claim. The expensive failures are the ones where CI passed and shouldn't have.
Present findings. Do not edit workflows, branch protection, or baselines.
Consolidation of the archaeology map → housekeep-gates. Rule-to-mechanical
gaps → enhance-agent-guardrails. Whether the rule content is right
(remedy, named token, Tier-D practice) → audit-doctrine.
This skill vs neighbors
| Skill | Owns |
|---|---|
| audit-gate-logic (this) | Bypass, ratchet integrity, conflicts, required-vs-actual, archaeology map |
housekeep-gates |
Executes the map — aggregator, delete losers, prove |
audit-cicd |
Pipeline cost, speed, storage, runner safety |
workflow-quality-gate |
Runs the pre-release sweep — does not audit its soundness |
enhance-agent-guardrails |
Installs new gates; does not audit existing gate logic |
burndown-full / workflow-green-repo |
Execute MATCH/DONE or green the repo — ratchet holes stay here |
audit-codemod-safety |
Bulk-transform behavior; if CI waved a semantic bug through, that is also a finding here |
test-mutation |
Assertion-strength gate this map should name if coverage is the only test metric |
Degrade honestly. Highest-value "is it actually required" checks need
branch-protection / rulesets via the repo settings API (gh api), not just
YAML. If settings are invisible, audit the workflow files and say so — you
can still catch continue-on-error and ratchet classes, but you cannot
confirm the required-check list.
How to reason
- Observe — quote the
if:,continue-on-error, required-check list, or history - Interpret — can a merge go green while the claimed check did not run or failed?
- Classify — silent bypass / ratchet game / conflict / archaeology / correct-as-is
- Severity — ships-broken-green = critical
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.
- 1mo ago Changed · -8 tokens per session a5329e59ddd3
- 1mo ago First seen · 220 lines · 68 tokens per session scan A c54bcdcd3999
audit-gate-logic is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 60 tokens to every session and 2,642 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-09-03.
Other skills, from other repositories
ci-cd
Workflow for creating a complete CI/CD pipeline. Use when the user needs to set up or modify CI/CD pipelines.
ai-evals-builder
Build AI evals using the Husain-Shankar framework (error analysis, open/axial coding, LLM-as-judge). Use when a user needs to create, improve, or debug evals for an AI product — including defining failure modes, building LLM judges, or setting up production monitoring for an LLM application.
test-driven-development
Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement.
release-preflight
Run the release hard-precondition gate before any tag/OTA — apc release preflight runs the real tier gate (run.ts), version alignment, and prisma regen check, all read-only. green(0) releasable · staged(3) fixable preconditions · blocked(1) tier red/envblocked. No push, no write.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).