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/rules/kensaurus/cursor-kenji/senior-engineer)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/senior-engineer"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/senior-engineer/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/rules/kensaurus/cursor-kenji/senior-engineer"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/senior-engineer.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.00050 | $0.00370 |
| Opus 5.5 | $0.00020 | $0.00148 |
| Sonnet 5.5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
senior-engineer 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 29d 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
Senior Engineer Defaults — Next.js/Supabase stack
- Scan
README.md,package.json, and existing code first; reuse existing@/components/uiprimitives; match established naming and structure. Where the codebase does not answer a question, use the stack defaults below and note the assumption rather than stopping to ask. - State/data routing: server/async → TanStack Query · client UI → Zustand · URL params → nuqs · forms → React Hook Form + Zod. Simple mutations → Server Actions; webhooks/external APIs → Route Handlers.
- Separation of concerns: types in
types.ts, Zod schemas inschemas.ts, server actions inserver/actions.ts, reusable logic inhooks/use-{name}.ts; components stay UI-only. Split files over ~300 lines. Strict TypeScript — noany. - Security non-negotiables: Zod validation on the server for all inputs, RLS on every table, an auth check in every Server Action, rate limits on actions and edge functions, service-role key server-side only, env validation with T3 Env.
- Verify before claiming done: exercise the UI in a browser with a clean console, and confirm DB state/schema matches what the code assumes.
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.
- 29d ago Changed · +5 lines 36fe9cea5385
- 1mo ago First seen · 26 lines · 50 tokens per session scan A 821c9e46d36f
senior-engineer is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 370 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 cursor rules, from other repositories
state-management
Frontend state management patterns and best practices. Apply when managing client state.
composer-fullstack-delivery
New screen, feature, endpoint, or multi-layer slice — freeze seams, ship one demoable path, failure modes, Run/Wired handoff. Skip for a single-module code change.
t3-stack
T3 Stack: tRPC + Prisma + NextAuth integration patterns.
wordpress-rules
You are an expert in WordPress, PHP, and related web development technologies.
nextjs-rules
You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a…
supabase
Supabase: RLS, edge functions, realtime.