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 agentmods add commands/kensaurus/cursor-kenji/gate-logicgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWhat 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 | $0.00018 | $0.00254 |
| Opus 5 | $0.00009 | $0.00127 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
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 3d 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
Gate-Logic Audit
Run the audit-gate-logic skill: inventory every gate and test whether
it can be silently bypassed, whether a ratchet can lock in regressions,
whether two workflows' conditions both fire or both skip, and map
accreted duplicate gates (Phase 2.5 archaeology).
Read-only — rewrite no workflow or branch-protection setting.
Consolidation of the archaeology map stays on housekeep-gates. Pipeline
cost/speed stays on audit-cicd. Whether the rule is right (not merely
enforced) stays on /doctrine (audit-doctrine). Running the pre-release
sweep stays on workflow-quality-gate. Installing new gates stays on
enhance-agent-guardrails.
Highest-value "is it actually required" checks need branch-protection / rulesets via the repo settings API. If those are invisible, say so and audit the YAML alone.
The full playbook lives in the audit-gate-logic skill.
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.
- 3d ago First seen · 25 lines · 18 tokens per session scan A 19a3443ac576
gate-logic is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 254 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-31.
Other commands, from other repositories
commit-msg
Cursor tooling: skills, rules, subagents.
boot
Initialize agent, verify setup, and load rules.
code-review
Confidence-based code review checklist.
prp-new
Create new Product Requirement Prompt from scratch.
clean
Repository hygiene — clean temp files, organize execution folders.
context
Dynamic context management — status, clean, log, save, read.