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/intrafere/moto-autonomous-asi/developer-mode-gatesgit clone --depth 1 https://github.com/Intrafere/MOTO-Autonomous-ASIWrote 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/intrafere/moto-autonomous-asi/developer-mode-gates)<a href="https://agentmods.dev/rules/intrafere/moto-autonomous-asi/developer-mode-gates"><img src="https://agentmods.dev/badge/rules/intrafere/moto-autonomous-asi/developer-mode-gates.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.00007 | $0.00298 |
| Opus 5 | $0.00003 | $0.00149 |
| Sonnet 5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
developer-mode-gates 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.
What it actually says
Developer Mode Gates
Developer mode is a hidden frontend switch toggled by pressing Shift + Z + X. The state is stored in localStorage as developerModeSettingsEnabled and should stay centralized through developerModeEnabled props or the same storage key.
Known gated surfaces:
LeanOJ Proof Solverappears in the mode selector only while developer mode is enabled. If developer mode is turned off whileappMode === 'leanoj', the app should return to autonomous mode.- Supercharge checkboxes in Aggregator, Compiler, Autonomous, LeanOJ, and related role settings are developer-only. Start/request payloads must force
supercharge_enabledfalse unless developer mode is currently enabled. - Creativity Emphasis Boost checkboxes beside Aggregator, Autonomous, and LeanOJ start controls are developer-only for now. Start/request payloads must force
creativity_emphasis_boost_enabled=falseunless developer mode is currently enabled; keep this gate isolated so the feature can later move to standard mode cleanly. - Raw JSON settings editors and developer-only model/settings toggles are developer-only and should close or hide when developer mode is disabled.
- Boost copy may mention Supercharge only when developer mode is enabled.
When adding a new hidden or experimental frontend control, gate both the visible UI and any request/runtime payload field behind developer mode. Do not rely on hiding the checkbox alone.
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 · 18 lines · 7 tokens per session scan A 82fed804559f
developer-mode-gates is a cursor rule published in the GitHub repository Intrafere/MOTO-Autonomous-ASI (82 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 298 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.