agentleFS
renanflustosarenanflustosa/octo-cluster/.cursor/rules/cost-routing.mdc

octo-cluster / rules

Cursor rule3 starsChanged 23 days agoMITView on GitHub

Cost routing — tier first, no mid-task model switch, capped loops

The file

We split this cost-routing.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify: focused test on changed behavior first.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
cost-routing.mdc
---
description: Cost routing — tier first, no mid-task model switch, capped loops
alwaysApply: true
---

# Cost routing (lite)

Tier at start: L0 trivial · L1 local · L2 multi-file/tests · L3 architecture/hard bug · L4 critical.
Session model: L0 haiku · L1-L2 sonnet · L3-L4 opus. Mismatch → say once at start; never switch model mid-task (full cache rebuild).
Subagent only for broad fan-out search or verbose output; pass `model: haiku` for search. Else direct tools.
Retry cap: 2 failed attempts, same approach → stop, show evidence, propose escalation.
Verify: focused test on changed behavior first; widen only on failure.
Same manual task twice → propose script or skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.