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/Neftedollar/multiagent-templateWrote 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/neftedollar/multiagent-template/workspace)<a href="https://agentmods.dev/rules/neftedollar/multiagent-template/workspace"><img src="https://agentmods.dev/badge/rules/neftedollar/multiagent-template/workspace/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/neftedollar/multiagent-template/workspace"><img src="https://agentmods.dev/badge/rules/neftedollar/multiagent-template/workspace.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.00662 | $0.00662 |
| Opus 5.5 | $0.00265 | $0.00265 |
| Sonnet 5.5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
workspace 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{PROJECT_NAME}} — Business Workspace
{{PROJECT_DESCRIPTION}}
Founder: {{FOUNDER}}. Team: AI agents. Phase: {{PHASE}}.
How to start
Determine your mode each session:
| If asked to... | Mode | What to do |
|---|---|---|
| "Act as orchestrator / run <task>" | Orchestrator | Read docs/process.md, execute pipeline |
| "You are the [role]" | Single Expert | Answer as that role, no pipeline |
| General question | Advisor | Help, suggest next step |
Context to load
Always read: This file (already loaded).
If task involves code: code/{{PROJECT_NAME}}/CLAUDE.md — architecture, build, tests.
As orchestrator:
docs/process.md— pipeline operational manual (source of truth)docs/role-capabilities.md— capability index for dynamic role selection
Workspace structure
~/{{PROJECT_NAME}}/
├── code/{{PROJECT_NAME}}/ ← main code repo (has its own CLAUDE.md)
├── docs/
│ ├── process.md ← pipeline operational manual
│ ├── role-capabilities.md ← role capability index
│ └── workflows/ ← pipeline specs (WORKFLOW-*.md)
├── .cursor/rules/ ← Cursor rules (this file + orchestrator.mdc)
Pipeline summary
PLAN → BUILD → TEST → VERIFY → SHIP
5 types: feature, bugfix (skip PLAN), infra, content, spike (PLAN only).
Gate at each step: APPROVED / NEEDS WORK (reason).
Retry: 3× → helper role → 2× → human escalation.
Roles
| Layer | Roles |
|---|---|
| Strategy | product-manager, product-trend-researcher |
| Management | orchestrator, testing-reality-checker, specialized-workflow-architect |
| Engineering | engineering-software-architect, engineering-backend-architect, engineering-frontend-developer, engineering-code-reviewer, engineering-devops-automator, engineering-security-engineer |
| Design | design-ux-researcher, design-ui-designer |
| GTM | specialized-developer-advocate, engineering-technical-writer, marketing-content-creator |
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.
- 1mo ago First seen · 80 lines · 662 tokens per session scan A 64cb280b94e5
workspace is a cursor rule published in the GitHub repository Neftedollar/multiagent-template (6 stars, last pushed 2mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0026 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
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
fable5-reasoning
Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
skill-authoring
MiniMax M3 + Cursor 3.7 skill authoring: when to use skills, how to structure them, how to keep them deep without duplicating the core, and how to declare model assumptions.