auth-flows

A read-only review of how an application protects its routes and server actions with sign-in and authorization checks.

In plain words
What is it for?
It maps protected routes to their actual safeguards, checks uses of getSession(), and flags middleware that is the only protection. It does not review database row-level security or patch code.
Why use it?
It reveals routes that may appear protected but are missing a real server-side permission check. It also distinguishes identifying a signed-in user from confirming what that user may do.

Command

Install

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.

agentmods
npx agentmods add commands/kensaurus/cursor-kenji/auth-flows
Clone the repo
git clone --depth 1 https://github.com/kensaurus/cursor-kenji
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 168 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00168
Opus 5 $0.00012 $0.00084
Sonnet 5 $0.00005 $0.00034
Haiku 4.5 $0.00002 $0.00017

Measured yesterday against content hash 0059930ee857, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/auth-flows.md · 18 lines

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.

Changes

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.

  1. yesterday First seen · 18 lines · 24 tokens per session scan A 0059930ee857

Subscribe to this mod's changes

auth-flows is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 168 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.