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/n1snt/redux-mcpWrote 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/n1snt/redux-mcp/rule_main)<a href="https://agentmods.dev/rules/n1snt/redux-mcp/rule_main"><img src="https://agentmods.dev/badge/rules/n1snt/redux-mcp/rule_main/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/n1snt/redux-mcp/rule_main"><img src="https://agentmods.dev/badge/rules/n1snt/redux-mcp/rule_main.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.00160 | $0.00160 |
| Opus 5.5 | $0.00064 | $0.00064 |
| Sonnet 5.5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
rule_main 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 2mo 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
Main Rule
- Always write and run relevant tests after every change; do not ship until tests pass.
- Enforce strict typing everywhere: typed args, explicit function return types, and typed variable declarations.
- Keep files small and focused; split files before they become too long.
- Avoid duplication: do not repeat functions/logic; extract shared utilities.
- Keep code clean and simple; prefer readable, minimal solutions.
- Keep type definitions in a separate
types.ts(or module-specific*.types.ts) file, not mixed with function implementation files. - Add dependencies only via package manager commands (bun add, bun add -d, etc.); never manually edit package.json to add packages.
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.
- 2mo ago First seen · 15 lines · 160 tokens per session scan A ca1114d347b5
rule_main is a cursor rule published in the GitHub repository n1snt/redux-mcp (3 stars, last pushed 6mo ago), licensed MIT. It adds 160 tokens to every session, about $0.0006 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-08-31.
Other cursor rules, from other repositories
bdd-specs
Executable Gherkin specifications, layout, style, tags, offline by construction.
workflow
BDD delivery order, Gherkin spec before tests before code, definition of done, Rules Sync.
testing
Vitest conventions and the mandatory unit-test set.
python-code-validator
Validate generated Python at every step, not once at the end.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.
testing
Testpflicht für nicht-trivialen Code.