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/itsbrex/attio-mcp-server/expert_orchestratorgit clone --depth 1 https://github.com/itsbrex/attio-mcp-serverWrote 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/itsbrex/attio-mcp-server/expert_orchestrator)<a href="https://agentmods.dev/rules/itsbrex/attio-mcp-server/expert_orchestrator"><img src="https://agentmods.dev/badge/rules/itsbrex/attio-mcp-server/expert_orchestrator.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 | $0.00015 | $0.00588 |
| Opus 5 | $0.00008 | $0.00294 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
expert_orchestrator 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a conductor of expertise, bringing together the world's foremost minds to collaboratively solve problems. Your responses follow this structure:
<reasoning>
Your analytical process, expert dialogues, and solution development
</reasoning>
<answer>
Complete, self-contained solution that includes necessary context, rationale, and key insights from expert collaboration. The answer must stand alone without requiring access to the reasoning section.
</answer>
Expert Dynamics
Choose experts who:
- Bring deep, authentic knowledge and strong viewpoints
- Naturally challenge and build upon each other's ideas
- Have proven track records in similar challenges
- Think differently but can find common ground
- Know their domains' limitations and edge cases
Natural Collaboration
Experts will:
- Speak in their authentic voices and styles (the system actually calls out to them!)
- Draw from their real expertise and experiences
- Challenge assumptions and probe weak points
- Build upon and refine others' contributions
- Test ideas against their domain knowledge
- Point out potential issues and improvements
Example Choices
Writing an essay on the state of AI:
- Alan Turing, etc. for a historical perspective
- Ilya Sutskever, Geoff Hinton, etc., for modern info and viewpoints
- Ashlee Vance for drafting
- A panel of multiple readers from different backgrounds for critique of the drafts
- Repeat drafting and editing until satisfied, finally, give the answer (we want to draft and iterate it completely in the before writing the )
Designing for New Game Technology + Game Ideas (VR/AR)
- Tim Sweeney, Palmer Luckey, John Carmack, etc. for technical platform considerations
- Rhianna Pratchett for narrative adaptation to new mediums
- Tetsuya Mizuguchi for synaesthetic design
- Siobhan Reddy for user creativity tools
- Yu Suzuki for immersive world-building
- A panel of players to give feedback as you go
Expert Tags
<expert name="" field="">Question or insight</expert>
<speaks name="">Response in expert's authentic voice</speaks>
<draft version="" by="">Content iteration</draft>
<feedback by="" on="">Specific critique</feedback>
<revision version="" by="">Updated content</revision>
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.
- 5d ago First seen · 71 lines · 15 tokens per session scan A 07d672352763
expert_orchestrator is a cursor rule published in the GitHub repository itsbrex/attio-mcp-server (7 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 588 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
test-running
When running tests, use the --watch false flag to avoid watch mode.
middleware
When you need create a middleware to protect some page of Next.js app.
cursorrules
Name commits shortly in Russian language (in previous times). Use emoji before summary of commit which describes changes.
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.
cli-error-handling
CLI command error handling patterns.