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/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/part-1-and-part-2-cointeraction-architecture)<a href="https://agentmods.dev/rules/intrafere/moto-autonomous-asi/part-1-and-part-2-cointeraction-architecture"><img src="https://agentmods.dev/badge/rules/intrafere/moto-autonomous-asi/part-1-and-part-2-cointeraction-architecture/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/intrafere/moto-autonomous-asi/part-1-and-part-2-cointeraction-architecture"><img src="https://agentmods.dev/badge/rules/intrafere/moto-autonomous-asi/part-1-and-part-2-cointeraction-architecture.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.02754 | $0.02754 |
| Opus 5 | $0.01377 | $0.01377 |
| Sonnet 5 | $0.00551 | $0.00551 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
part-1-and-part-2-cointeraction-architecture 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 12d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Unified Mode Design:
This describes additional architecture for the synergy between the part 1 database aggregator tool and part 2 aggregator-compiler tool. Both modes operate identically in default and generic deployment — the only difference is provider availability (see hosted-web-contract.mdc for details on generic mode).
NOTE: This is a continuously-running program that does not stop itself; the user selects one top-level workflow mode to run and turns it off when desired. There is no "solution stop token" as in normal AI solution generation.
Aggregator start-up workflow
1.) The aggregator runs initially with no compiler running. 2.) The compiler does not begin running until the user starts it manually, and current code enforces that Aggregator, Compiler, Autonomous Research, and LeanOJ Proof Solver are mutually exclusive top-level modes. Aggregator can run on its own without any compilation.
GUI Design
The user should be able to save any mid-way progress of the aggregation database and the current compilation results separately as the program is still running.
The live-constructing aggregation results should be viewable in one tab and also a save function that allows the user to save the whole current aggregation database to a .txt file. This aggregation database should be viewable in rea-time as the aggregation submittors write it.
The live-constructing compiler-written paper should be viewable in one tab and also a save function that allows the user to save the whole current aggregation database to a .txt file. This paper should be viewable in real-time as the compiler constructs it.
Manual mode prompts are durable run state. Aggregator and Compiler prompts must persist across stop, crash, restart, and repeated continue/start cycles, and must only be cleared by the explicit user clear/reset action for that mode. Empty/default startup state must never overwrite a previously saved prompt.
Generic mode frontend note: In generic mode the MOTO sandbox is API-only — the React frontend is served by the Web Team's separate website, not from the sandbox. The frontend calls GET /api/features on mount and hides LM Studio UI options when generic_mode=True. All other frontend functionality is identical.
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.
- 12d ago First seen · 106 lines · 2,754 tokens per session scan A d6482b7929dc
part-1-and-part-2-cointeraction-architecture is a cursor rule published in the GitHub repository Intrafere/MOTO-Autonomous-ASI (82 stars, last pushed 8d ago), licensed MIT. It adds 2,754 tokens to every session, about $0.0138 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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.