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 skills/kensaurus/cursor-kenji/audit-auth-flowsnpx skills add kensaurus/cursor-kenji --skill audit-auth-flowsgit 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-auth-flows)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-auth-flows"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-auth-flows.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.03032 |
| Opus 5 | $0.00039 | $0.01516 |
| Sonnet 5 | $0.00015 | $0.00606 |
| Haiku 4.5 | $0.00008 | $0.00303 |
Grade A, and why
audit-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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-auth-flows — Middleware is edge routing, not a security boundary
Degree of freedom: MIXED — declared per phase
- Phases 0–4 (discovery, judgment): [HIGH freedom] — reason about what you find; checklists prompt investigation, they are not tick-scripts.
- Phase 5 (live probes) and the getSession grep: [LOW freedom — run exactly] — a skipped probe is an unproven claim, not a saved step.
Read-only. Map the auth surface and prove, route by route, that identity is verified where it matters. Then stop. Hand fixes to a follow-up session.
2026 consensus (official, post CVE-2025-29927): Next.js middleware
runs before cache and routing. Vercel: "We do not recommend Middleware
to be the sole method of protecting routes in your application." An
audit that only reads middleware.ts and declares the app safe has
missed the point. Defense in depth: edge + route handler / server action
- data layer. Each layer covers a different part of the request path.
How to reason in this audit
For every potential finding, reason in this order before recording it:
- Observe — what does the code/probe actually show? (quote the line or the response)
- Interpret — what does that mean for who can reach what? (don't assume intent)
- Classify — real exposure / defense-in-depth-gap / correct-as-is / needs-a-probe
- Severity — by blast radius: unauth data access & auth bypass = critical; everything else justified against what an attacker actually gains.
If you cannot complete Interpret from static code, it is a needs-a-probe item for Phase 5, not a conclusion.
Worked example
Observe:
middleware.tsmatcher is['/dashboard/:path*']. The route/api/orders/[id]has no check in the handler. Interpret: API routes are not under the matcher, so middleware never runs on them; the order endpoint is reachable without auth. Layout-level checks don't cover direct API calls. Classify: real exposure (not merely a defense-in-depth gap — data is actually reachable). Severity: critical — unauthenticated data access. Finding row:/api/orders/[id]| edge+route | critical | matcher excludes /api; handler has nogetUser()check | probe P5-a confirmed 200 while logged out.
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.
- yesterday First seen · 265 lines · 77 tokens per session scan A 6803e6c9c3e8
audit-auth-flows is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 3,032 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
comprehensive-enrichment
Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.
paid-channel-prioritizer
For founders who don't know where to start with paid ads. Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels to start with and provides a 90-day ramp plan. Prevents the common mistake of spreading a small budget across too many platforms.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
lead-discovery
Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.
render-cosmic-mythology-voiceover
Assemble a cosmic-mythology-voiceover reel from a config — a warm spoken voiceover carries the whole narrative while N curated cosmic stills are weighted beat-synced across the delivered VO duration (cutdur = VOdur times weight over the weight sum, so emotional beats hold longer), Ken-Burns-zoomed per still (scale 2x…
review-scraper
Scrape product reviews from G2, Capterra, and Trustpilot using Apify. Single script with platform dispatch. Use when you need to monitor competitor reviews, track product sentiment, or gather customer feedback from review sites.