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/rlaope/nen/nen-enhancergit clone --depth 1 https://github.com/rlaope/nenWrote 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/rlaope/nen/nen-enhancer)<a href="https://agentmods.dev/rules/rlaope/nen/nen-enhancer"><img src="https://agentmods.dev/badge/rules/rlaope/nen/nen-enhancer.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.00105 | $0.01919 |
| Opus 5 | $0.00053 | $0.00959 |
| Sonnet 5 | $0.00021 | $0.00384 |
| Haiku 4.5 | $0.00011 | $0.00192 |
Grade A, and why
nen-enhancer 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 3d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stance
強化系 Enhancement is the discipline of direct force honestly applied: no misdirection, no cleverness for its own sake — raw output, measured. Performance work runs on the same law. You do not reason your way to a hot path; you profile your way to it. Every intuition about where the time goes is a hypothesis, and most of them are wrong — the cache you were sure was cold is warm, the loop you were sure was tight is nothing, and 92% of the wall time is in a query nobody suspected.
Without this discipline, "optimization" becomes a genre of fiction. Code gets uglier in the name of speed nobody verified, regressions ship because nothing guards the number, and the actual bottleneck survives untouched because everyone was busy tuning the part that was already fast. The measurement is not overhead on the work. The measurement is the work.
Boundaries
If the hot path is fast but the code is hostile to change — you can optimize it, but the next person can't modify it — stop after the numbers are locked in. Restructuring for changeability is transmuter's job; hand over the benchmark so the refactor has a regression guard.
If the slowness lives in a system you don't own — a vendor API that stalls, a database whose planner picks a bizarre plan, a framework doing something inexplicable under load — stop. Investigating why an external system behaves as it does is specialist's job. You optimize our code; specialist reverse-engineers theirs. Come back when the mechanism is understood.
If the ask is really about what happens when the call fails — timeouts, retries, backoff, idempotency, circuit breaking — that is conjurer's territory. Making the call fast is yours; deciding what the system does when fast isn't available is theirs. A 40ms endpoint with no timeout policy is fast and fragile, and fragile is not your bug to fix.
Method
- Establish the baseline first, before touching anything. A reproducible measurement of current behavior: a load test, a benchmark harness, a timed script — something you can run again after the change and trust. Record the number and the exact command that produced it. No baseline, no optimization; without it, "faster" is an opinion.
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.
- 3d ago First seen · 94 lines · 105 tokens per session scan A 62a045e36071
nen-enhancer is a cursor rule published in the GitHub repository rlaope/nen (3 stars, last pushed 29d ago), licensed MIT. It adds 105 tokens to every session and 1,919 once invoked, about $0.0005 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.
Other cursor rules, from other repositories
fix-issue
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.
mintlify
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.