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/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/project-overview)<a href="https://agentmods.dev/rules/c9r-io/orchestrator/project-overview"><img src="https://agentmods.dev/badge/rules/c9r-io/orchestrator/project-overview/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/c9r-io/orchestrator/project-overview"><img src="https://agentmods.dev/badge/rules/c9r-io/orchestrator/project-overview.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.00368 | $0.00368 |
| Opus 5.5 | $0.00147 | $0.00147 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
project-overview 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 2mo 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
AI Dev Platform Overview
This repository is an AI-first development scaffold. The expected workflow is:
- Bootstrap a new project using the
project-bootstrapskill. - Plan changes explicitly (scope, acceptance criteria, risks, test plan).
- Implement code with conventions (see Rust/Testing rules).
- Convert the approved plan into reproducible QA docs via
qa-doc-gen. - Execute QA docs and create tickets via
qa-testing. - Fix failures end-to-end via
ticket-fix.
Repository Conventions (from project-bootstrap)
Projects generated by project-bootstrap typically have:
core/ # backend service (language/framework may vary)
portal/ # frontend (optional)
docker/ # Dockerfiles and docker-compose.yml
k8s/ # Kubernetes manifests (base overlays)
deploy/ # deploy/upgrade/cleanup scripts
scripts/ # local helper scripts (including reset)
docs/qa/ # reproducible QA documents (inputs for qa-testing)
docs/ticket/ # failure tickets (inputs for ticket-fix)
Operational entry points:
- Local run:
docker compose -f docker/docker-compose.yml up -d --build - Reset:
./scripts/reset-docker.sh - K8s deploy:
./deploy/deploy.sh - K8s upgrade/rollout:
./deploy/upgrade.sh
Rules of Engagement
- Prefer deterministic steps and evidence: commands, outputs, and minimal diffs.
- When a plan is approved, treat
docs/qaas the executable acceptance spec. - If a QA scenario fails, capture evidence and open a ticket under
docs/ticket/.
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.
- 2mo ago First seen · 44 lines · 368 tokens per session scan A 324520c77d44
project-overview is a cursor rule published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It adds 368 tokens to every session, about $0.0015 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-30.
Other cursor rules, from other repositories
rust-cli-conventions
Conventions for the CLI/TUI, provider abstraction, tool safety, and agent loop.
rust-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.
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.