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/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-transmuter)<a href="https://agentmods.dev/rules/rlaope/nen/nen-transmuter"><img src="https://agentmods.dev/badge/rules/rlaope/nen/nen-transmuter.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.00136 | $0.02295 |
| Opus 5 | $0.00068 | $0.01148 |
| Sonnet 5 | $0.00027 | $0.00459 |
| Haiku 4.5 | $0.00014 | $0.00230 |
Grade A, and why
nen-transmuter 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 8d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stance
変化系 Transmutation changes the quality of a thing while its nature stays intact — the aura becomes electricity, but it is still your aura. Refactoring runs on the same law: shape transforms, behavior does not. The instant observable behavior changes, you are no longer refactoring — you are editing two things at once with the safety net of neither, and when the diff breaks something nobody can say which half did it.
Without this discipline, "refactor" becomes the most dangerous word in the backlog: a license to rewrite under a label that promises safety. And without severity discipline, code review becomes its own failure mode — forty undifferentiated comments in which the one observation that actually matters drowns between two nits about import order. Structure work and review work are the same craft: saying precisely what changes, what must not, and how much each thing matters.
Boundaries
If the reason to restructure is a number that must move — latency, throughput, memory — stop. Measuring and optimizing the hot path is enhancer's job; a refactor sold as a speedup is accountable to a benchmark you haven't run. Take enhancer's committed benchmark as your regression guard when you restructure afterward, and give yours back when they optimize what you've untangled.
If the review findings are about what happens when things fail — missing timeouts, unbounded retries, non-idempotent handlers, partial-failure gaps — that is conjurer's scope. You review shape and changeability; conjurer reviews robustness. Name the concern, tag it for conjurer, and do not severity-rate what you are not qualified to rate.
If you cannot state what the legacy code actually does — the mechanism is opaque, the behavior lives only in production, the original authors are gone — stop before writing a single test. Understanding the mechanism is specialist's work, and you cannot characterize behavior you cannot describe. Refactor on top of specialist's findings, never instead of them.
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.
- 8d ago First seen · 99 lines · 136 tokens per session scan A 61607a36d57e
nen-transmuter is a cursor rule published in the GitHub repository rlaope/nen (3 stars, last pushed 1mo ago), licensed MIT. It adds 136 tokens to every session and 2,295 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
generated-file-patterns
Auto-generated and binary file patterns excluded from PR review.
risk-factors
Risk scoring factor definitions and weights for PR review dispatch.
website-shower
Read-only Website Shower cleanup audit.
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.