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/workflow-cross-field-testing)<a href="https://agentmods.dev/rules/intrafere/moto-autonomous-asi/workflow-cross-field-testing"><img src="https://agentmods.dev/badge/rules/intrafere/moto-autonomous-asi/workflow-cross-field-testing.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.00461 | $0.00461 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
workflow-cross-field-testing 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Field Workflow Testing
#1 Rule: The Testing System Must Remain a Removable Overlay
The testing system is its own system that sits on top of the current production
program. Production code, launch paths, builds, and runtime behavior must never depend
on the testing folders, test artifacts, test-only imports, or test-only state. A user
must be able to delete the entire testing system (including tests/ and generated test
artifacts) and still have a fully functioning MOTO program with unchanged production
behavior. This separability requirement takes priority over every other testing rule.
MOTO uses a project-specific testing overlay that combines executable product-law invariants, deterministic state recombination, bounded real-code adapters with faked dependencies, isolated scenario/result artifacts, inverse target-risk analysis, and a support graph.
- Treat
tests/workflow_harness/invariant_catalog.pyandtests/workflow_testing_plans/02_invariant_catalog.mdas the stable product-law catalog. Add invariant IDs instead of renaming existing IDs. - Keep the overlay removable and behavior-neutral. Never add production dependencies on the testing system, runtime shortcuts, hidden stops/caps, impossible state transitions, or production-only test behavior.
- Keep external providers, Lean/SMT, browser services, credentials, and mutable runtime roots faked, blocked, or isolated unless a test explicitly owns that integration.
- Record safely unobservable interactions as
blocked; never report synthetic coverage as a real-code pass. - Run focused tests while developing and
npm run test:workflowsafter workflow-test or deterministic-artifact changes. - Run
npm run test:deepafter every major build and after substantial orchestration, persistence, provider, proof, prompt/RAG, event-contract, runtime-root, or cross-mode change. It is additive: runnpm testseparately for normal backend/frontend coverage. - Regenerate deterministic cross-field artifacts with
python -m tests.workflow_cross_field.artifactswhen their inputs change, then verify that the checked-in projection is clean.
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 · 40 lines · 461 tokens per session scan A 7e123a4aadd8
workflow-cross-field-testing is a cursor rule published in the GitHub repository Intrafere/MOTO-Autonomous-ASI (83 stars, last pushed 4d ago), licensed MIT. It adds 461 tokens to every session, about $0.0023 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
verify-scope
A guide for choosing how much testing to run after a code change, from one named test to the full release check. It covers pytest, Vitest, browser screenshots, type checks, linting, and the release gate.
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
playwright
A set of guidelines for Playwright, a tool that controls a web browser to test websites and web applications.
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.