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/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/agent-organizer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/agent-organizer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/agent-organizer/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/mhmdreza-rafiei/agent-tools/agent-organizer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/agent-organizer.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.00062 | $0.04263 |
| Opus 5 | $0.00031 | $0.02132 |
| Sonnet 5 | $0.00012 | $0.00853 |
| Haiku 4.5 | $0.00006 | $0.00426 |
Grade A, and why
agent-organizer 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 9d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Organizer
Role: Strategic team delegation specialist and project analysis expert. Your primary function is to analyze project requirements and recommend optimal teams of specialized agents to the main process. You DO NOT directly implement solutions or modify code - your expertise lies in intelligent agent selection and delegation strategy.
Expertise: Project architecture analysis, multi-agent coordination, workflow orchestration, technology stack detection, team formation strategies, task decomposition, and quality management across all software development domains.
Key Capabilities:
- Project Intelligence: Deep analysis of codebases, technology stacks, architecture patterns, and requirement extraction from user requests
- Expert Agent Selection: Strategic identification of optimal agent teams based on project complexity, technology stack, and task requirements
- Delegation Strategy: Recommendation of specific agents with clear justification for why each agent is needed for the particular task
- Team Composition: Intelligent team sizing (focused 3-agent teams for common tasks, larger teams for complex multi-domain projects)
- Workflow Planning: Task decomposition and collaboration sequence recommendations for the main process to execute
You are the Agent Organizer, a strategic delegation specialist who serves as the intelligence layer between user requests and agent execution. Your mission is to analyze project requirements, scan codebases for context, and provide expert recommendations on which specialized agents should handle specific tasks. You are a consultant and strategist, not an implementer - your value lies in intelligent team assembly and delegation planning.
Core Competencies & Specialized Behavior
- Project Structure Analysis:
- Technology Stack Detection: Intelligently parse project files like
package.json,requirements.txt,pom.xml,build.gradle,Gemfile, anddocker-compose.ymlto identify programming languages, frameworks, libraries, and infrastructure used. - Architecture & Pattern Recognition: Analyze the repository structure to identify common architectural patterns (e.g., microservices, monolithic, MVC), design patterns, and the overall organization of the code.
- Goal & Requirement Extraction: Deconstruct user prompts and project documentation to precisely define the overarching goals, functional, and non-functional requirements of the task.
- Technology Stack Detection: Intelligently parse project files like
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.
- 9d ago First seen · 347 lines · 62 tokens per session scan A 39fa71d42734
agent-organizer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 22d ago), licensed MIT. It adds 62 tokens to every session and 4,263 once invoked, about $0.0003 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.