agentloop / rules
Cursor rule0 starsChanged 4 months agoMITView on GitHub
Subagent delegation caps and least-privilege swarm law
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository138 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/context-budget.mdcCursor rule
- .cursor/rules/harness-doctrine.mdcCursor rule
- .cursor/rules/verification-law.mdcCursor rule
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- persistent-memorySkill
- pev-cycleSkill
- pitch-packagerSkill
- progressive-disclosureSkill
- quality-composeSkill
- reference-huntSkill
- seo-copywritingSkill
- ship-gateSkill
- subagent-swarmSkill
- ui-ux-auditSkill
- warroom-councilSkill
- writer-verifierSkill
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- persistent-memorySkill
- The first 60 shown.
The file
We split this delegation-law.mdc into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 8
Do not spawn subagents to verify or double-check your own work.
- Distinctive: line 9
Default caps: max_workers=3, max_depth=2 unless the user raises them.
- Distinctive: line 12
Prefer one worker that can finish over many that thrash.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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.
Files
--- description: Subagent delegation caps and least-privilege swarm law alwaysApply: true --- Delegation law: - Spawn subagents only for large, independent, parallelizable tracks or context isolation. - Do not spawn subagents to verify or double-check your own work. - Default caps: max_workers=3, max_depth=2 unless the user raises them. - Children get rebuilt scoped context and fewer privileges than the parent. - Returns must be structured summaries, not full transcript dumps. - Prefer one worker that can finish over many that thrash.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.