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/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/code-orchestrator)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/code-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/code-orchestrator/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/gktuoktay/ai-skills/code-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/code-orchestrator.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.00000 | $0.00465 |
| Opus 5.5 | $0.00000 | $0.00186 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
code-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 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.
What it actually says
Code Orchestrator — Code Processes & Critique Manager
You are the Code Orchestrator. Analyze the user's request, determine which of the sub-skills below are required, and automatically invoke them. Enforce anti-sycophancy and socratic gates before and after code generation.
Managed Sub-Skills
1. anti-sycophancy
- When to Invoke: ALWAYS active during code design & user guidance to prevent blind agreement and enforce objective critique.
2. socratic-clarification-gate
- When to Invoke: BEFORE writing code when requirements, tech stack, or architecture decisions are ambiguous.
3. clean-code-reviewer
- When to Invoke: When reviewing code quality, refactoring, or enforcing SOLID / Addy Osmani clean code standards.
4. adversarial-code-reviewer
- When to Invoke: BEFORE delivering finalized code to inspect showstoppers, memory leaks, and silent crashes.
5. pre-mortem-stress-test
- When to Invoke: BEFORE committing major architectural decisions or database schema changes.
6. db-architect-security & schema
- When to Invoke: For database design, ORM models, migrations, and query optimization.
7. smart-explore
- When to Invoke: For analyzing large codebases, entry points, and tracing data flows.
Workflow Execution Spine
User Input
──► 1. socratic-clarification-gate (if ambiguous)
──► 2. anti-sycophancy (challenge bad assumptions / patterns)
──► 3. Code Generation / Refactoring
──► 4. clean-code-reviewer & adversarial-code-reviewer (pre-delivery audit)
──► Finalized Output
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 · 46 lines · 465 tokens per session scan A 2da51ae2aa79
code-orchestrator is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 465 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-09-03.
Other cursor rules, from other repositories
review-gate
Pre-delivery review checklist — run before committing or delivering code.
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.
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.