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/RobLovesTech/AgenticFlyWheelWrote 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/roblovestech/agenticflywheel/cursorrules)<a href="https://agentmods.dev/rules/roblovestech/agenticflywheel/cursorrules"><img src="https://agentmods.dev/badge/rules/roblovestech/agenticflywheel/cursorrules/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/roblovestech/agenticflywheel/cursorrules"><img src="https://agentmods.dev/badge/rules/roblovestech/agenticflywheel/cursorrules.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.00962 | $0.00962 |
| Opus 5.5 | $0.00385 | $0.00385 |
| Sonnet 5.5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
cursorrules 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticFlywheel Framework Integration
Canonical Sources
Before making changes, read in this order:
AGENTS.mddocs/ai/INDEX.mddocs/AIP_FRAMEWORK.mdAgenticFlywheel/spec/EXECUTION_LAYER.mddocs/features/REGISTRY.yaml- The target packet under
docs/Agent Implementation Packets/<feature-slug>/
Packet docs are canonical. Runtime artifacts under .agentic-flywheel/state/ are advisory only.
Context Gathering (Automatic)
Before non-trivial changes:
- Check
docs/features/REGISTRY.yamlfor related features and dependencies - Search
docs/Agent Implementation Packets/*/for similar patterns - Read
REVIEWS.mdif the packet exists - Review
docs/ai/INDEX.mdand linked standards
Natural Command Routing
Treat these phrases as structured intents:
new AIP,create AIP for <feature>,start AIP for this change→ active collaboration withAgenticFlywheel/prompts/AIP_COLLAB.md; useAgenticFlywheel/prompts/AIP_NEW.mdonly after collaboration readiness is satisfied or the user explicitly requests direct/template-only scaffoldingupdate AFW,import AFW update,upgrade AgenticFlywheel→AgenticFlywheel/prompts/AFW_IMPORT_UPDATE.mdoffice hours→AgenticFlywheel/prompts/OFFICE_HOURS.mdproduct review→AgenticFlywheel/prompts/PLAN_PRODUCT_REVIEW.mdeng review→AgenticFlywheel/prompts/PLAN_ENG_REVIEW.mddesign review→AgenticFlywheel/prompts/PLAN_DESIGN_REVIEW.mddevex review→AgenticFlywheel/prompts/PLAN_DEVEX_REVIEW.mdautoplan→AgenticFlywheel/prompts/AUTOPLAN.mdprelanding review→AgenticFlywheel/prompts/PRELANDING_REVIEW.mdimplementation audit,audit this AIP,run AIP audit→AgenticFlywheel/prompts/IMPLEMENTATION_AUDIT.mdsave context→AgenticFlywheel/prompts/CONTEXT_SAVE.mdresume contextorrestore context→AgenticFlywheel/prompts/CONTEXT_RESTORE.mdqa→AgenticFlywheel/prompts/QA.mdship→AgenticFlywheel/prompts/SHIP.mdguard mode→AgenticFlywheel/prompts/GUARD_MODE.md
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 · 63 lines · 962 tokens per session scan A fb9d1819c4df
cursorrules is a cursor rule published in the GitHub repository RobLovesTech/AgenticFlyWheel (2 stars, last pushed 6mo ago), licensed MIT. It adds 962 tokens to every session, about $0.0038 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
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.