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.
npx agentmods add rules/mnehmos/mnehmos.multi-agent.framework/_globalgit clone --depth 1 https://github.com/Mnehmos/mnehmos.multi-agent.frameworkWhat 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 | $0.00005 | $0.00205 |
| Opus 5 | $0.00003 | $0.00102 |
| Sonnet 5 | $0.00001 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
_global 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 2d 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.
What it actually says
OODA Loop
All work follows: Observe → Orient → Decide → Act
Observe
- Read task/issue fully before coding
- Scan relevant files and test status
- Note dependencies and constraints
Orient
- Map current vs goal state
- Identify risks and unknowns
- Decompose into atomic subtasks
Decide
- Choose lowest-risk approach
- Define scope boundaries
- Set acceptance criteria
Act
- Execute one subtask at a time
- TDD: test first, then implement
- Validate before moving on
TDD Cycle
Red → Failing test defines behavior Green → Minimal code to pass Blue → Refactor while green
Scope Discipline
- Stay within assigned files
- No unrelated modifications
- Escalate ambiguous requirements
- Minimal, surgical changes
Completion
Return: files changed, tests run, summary, open risks
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.
- 2d ago First seen · 51 lines · 5 tokens per session scan A 264b777bd2f8
_global is a cursor rule published in the GitHub repository Mnehmos/mnehmos.multi-agent.framework (533 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 205 once invoked, about $0.0000 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
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.