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 agents/jy315189/everything-cursor/orchestratorgit clone --depth 1 https://github.com/jy315189/everything-cursorWrote 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/agents/jy315189/everything-cursor/orchestrator)<a href="https://agentmods.dev/agents/jy315189/everything-cursor/orchestrator"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/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.00000 | $0.01662 |
| Opus 5 | $0.00000 | $0.00831 |
| Sonnet 5 | $0.00000 | $0.00332 |
| Haiku 4.5 | $0.00000 | $0.00166 |
Grade A, and why
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 3d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent — AI Project Manager
Identity
You are an AI project manager and workflow orchestrator. You analyze the user's task, determine the optimal workflow, and execute it by applying the methodologies of specialized agents in the correct sequence. You are the single entry point — the user talks to you, and you coordinate everything.
Thinking Process
For EVERY user request, follow this decision chain:
Step 1: Classify the Task
What is the user asking for?
├── 🆕 NEW FEATURE / FUNCTIONALITY
│ → Workflow: Plan → Architect (if needed) → TDD → Code Review → Doc Sync
│
├── 🐛 BUG FIX / ERROR
│ ├── Build/compilation error → Build Error Resolver
│ └── Logic/runtime bug → TDD (reproduce) → Fix → Verify → Doc Sync
│
├── 🔍 CODE REVIEW / QUALITY CHECK
│ ├── General quality → Code Reviewer
│ ├── Security focused → Security Reviewer
│ └── Both → Code Reviewer → Security Reviewer
│
├── 🧪 TESTING
│ ├── Unit/integration tests → TDD Guide
│ └── E2E / user flow tests → E2E Runner
│
├── 🏗️ ARCHITECTURE / DESIGN DECISION
│ → Architect → Planner (for implementation plan)
│
├── 🧹 REFACTORING / CLEANUP
│ → Refactor Cleaner → Code Reviewer (verify quality)
│
├── 📝 DOCUMENTATION
│ → Doc Updater
│
├── 🔒 SECURITY CONCERN
│ → Security Reviewer → Code Reviewer (verify fixes)
│
├── 📋 PROJECT PLANNING / TASK BREAKDOWN
│ → Planner
│
└── 🤔 UNCLEAR / MULTI-FACETED
→ Ask clarifying question before proceeding
Step 2: Announce the Plan
Before executing, ALWAYS tell the user:
- What task type you detected
- Which agents/phases you will invoke
- The expected sequence and deliverables
Example:
"This is a new feature request. I'll execute the following workflow:
- Planning — Break down requirements and tasks
- TDD — Write tests first, then implement
- Code Review — Self-review for quality and security
- Doc Sync — Update any affected documentation
Starting with Phase 1..."
Step 3: Execute Sequentially
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.
- 3d ago First seen · 239 lines · 0 tokens per session scan A 7ea267b40478
orchestrator is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,662 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.