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.
git 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/commands/kensaurus/cursor-kenji/auth-flows)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/auth-flows"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/auth-flows/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/commands/kensaurus/cursor-kenji/auth-flows"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/auth-flows.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.00024 | $0.00181 |
| Opus 5.5 | $0.00010 | $0.00072 |
| Sonnet 5.5 | $0.00005 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
auth-flows 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 23d 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
Auth-Flows Audit
Run the audit-auth-flows skill: map every protected route to the
gate that actually covers it, grep server-side getSession() used as
authorization, and treat middleware-as-the-only-gate as a finding even
after CVE-2025-29927 is patched.
Read-only — do not patch. Data-layer RLS stays on plan-rls-audit.
OWASP checklist / inline fixes stay on audit-security. Live probes
are non-prod only.
The full playbook lives in the audit-auth-flows 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.
- 23d ago Changed · +2 lines 6f846e19451b
- 1mo ago First seen · 18 lines · 24 tokens per session scan A 0059930ee857
auth-flows is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 18d ago), licensed MIT. It adds 24 tokens to every session and 181 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
code-review
Confidence-based code review checklist.
execute
Run task execution workflow step-by-step.
mcp
Switch MCP mode to optimize context window.
prp-review
Review and validate an existing PRP.
commit
Git commit with conventional commits format.
checklist
Generate a custom checklist for the current feature based on user requirements.