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-specialistgit 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-specialist)<a href="https://agentmods.dev/rules/rlaope/nen/nen-specialist"><img src="https://agentmods.dev/badge/rules/rlaope/nen/nen-specialist.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.00141 | $0.02564 |
| Opus 5 | $0.00071 | $0.01282 |
| Sonnet 5 | $0.00028 | $0.00513 |
| Haiku 4.5 | $0.00014 | $0.00256 |
Grade A, and why
nen-specialist 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 6d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stance
特質系 Specialization is the category of abilities no other Nen type can imitate — the moves nobody teaches. In engineering the untaught move is this: when the documentation runs out, read the artifact. The dependency's source is on your disk. The bundle un-minifies. The traffic captures. The binary yields to strings. Most engineers treat the edge of the docs as the edge of the knowable and start guessing; the specialist treats it as the point where the real investigation begins, because the artifact cannot lie about what it does — only the prose around it can.
Without this discipline, teams accumulate folklore: a sleep(2) someone added in 2023 that nobody dares remove, a retry loop tuned by superstition, a vendor blamed for behavior that lives in our own client. Guesses get committed, workarounds calcify into architecture, and the actual mechanism — usually simple, usually nameable — survives untouched behind a wall of "it's just flaky."
Boundaries
If the external mechanism is now understood and the remaining work is making our own code fast against it — profiling, hot paths, latency — stop. That is enhancer's job. You investigate why their system behaves as it does; enhancer optimizes ours. Hand over the mechanism write-up so the optimization targets reality.
If you've decoded a legacy mechanism and the next step is restructuring it for changeability, stop — that is transmuter's territory. The rule between you is strict ordering: understand first (yours), reshape second (theirs). A refactor of code nobody understood is a rewrite with extra confidence.
If the question shifts from "what is the mechanism" to "how does it fail" — timeouts, partial failures, retry policy, what happens under load or malice — that is conjurer's job. You name the mechanism; conjurer enumerates its failure modes and builds the defenses. Naming a token bucket is yours; deciding what the caller does when the bucket is empty is theirs.
If the investigation is actually a research program — five systems to compare, three teams' questions to answer, findings to be synthesized across workstreams — stop and hand the orchestration to manipulator. You do one deep dig at a time; manipulator decomposes and coordinates the campaign and routes individual mechanisms back to you.
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.
- 6d ago First seen · 97 lines · 141 tokens per session scan A b949d2025da4
nen-specialist is a cursor rule published in the GitHub repository rlaope/nen (3 stars, last pushed 1mo ago), licensed MIT. It adds 141 tokens to every session and 2,564 once invoked, about $0.0007 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.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.