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 rules/kensaurus/cursor-kenji/_projectgit 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/_project)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/_project"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/_project.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.1 | $0.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
_project 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project conventions
Targets
android/— native Android (Kotlin/Java/Gradle)ios/— native iOS (Swift/Obj-C/Xcode)src/— shared React Native JS/TSweb/— web build (separate target)
Adjust these paths if your monorepo uses a different layout (e.g.
apps/mobile/{android,ios,src}/orpackages/web/).
Developer environment (CRITICAL)
The developer is on Linux/Windows, NOT macOS. This means:
- iOS cannot be built or tested locally. Do NOT suggest
xcodebuild,pod install,xcrun simctl, Xcode, or any other macOS-only tool for the developer to run locally. - iOS verification happens entirely on GitHub Actions CI with macOS runners.
- iOS distribution happens via TestFlight — the developer installs builds on a real iPhone from TestFlight after CI uploads them.
- Android local dev uses ADB + Android emulator + Metro for hot reload.
- For iOS-affecting changes, the loop is: edit → verify TS / lint / Android compile locally → push → CI builds iOS → TestFlight → install on device.
When the developer reports an iOS issue, the diagnostic path is:
- Check shared JS for the issue first (90%+ of "iOS bugs" are actually JS/RN issues that also reproduce on Android).
- If it's iOS-specific (native bridge,
Podfile, iOS-only code), edit the file and trigger CI — do not ask the developer to "run pod install" or "open Xcode." - Use
/ios-ci-logsto diagnose CI failures.
Hard rules
- Identify the target before editing. The path tells you which.
- Do NOT mix patterns across targets:
- No JSX/React in
android/orios/ - No native bridge code in
src/ - No
react-nativeimports inweb/(unlessreact-native-webis configured) - No browser APIs (
window,document,localStorage) insrc/
- No JSX/React in
- Never declare a task complete without running the verification command for the affected target.
- For iOS-affecting changes: declare "ready to ship to CI" — never claim "iOS verified" since you cannot.
- TypeScript strict; do not introduce
anywithout an inline justification comment. - Never disable a lint rule inline without an explanatory comment.
- Never commit secrets, signing keys,
local.properties,.env, or*.keystore.
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.
- 2d ago First seen · 70 lines · 703 tokens per session scan A 50b503307fe3
_project is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 7d ago), licensed MIT. It adds 703 tokens to every session, about $0.0035 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 cursor rules, from other repositories
mobile
Rules for mobile development (Swift/iOS, Kotlin Android, React Native, Flutter).
expo
Expo/React Native: native modules, navigation, platform-specific code.
react-native
React Native: mobile app development, navigation, native modules.
flutter
Flutter: Riverpod, widget extraction, Dart 3.
01-tech-stack
Android tech stack and project standards.
03-ui
UI, layout, theming and localization standards.