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/remix-conventions)<a href="https://agentmods.dev/rules/c9r-io/orchestrator/remix-conventions"><img src="https://agentmods.dev/badge/rules/c9r-io/orchestrator/remix-conventions/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/remix-conventions"><img src="https://agentmods.dev/badge/rules/c9r-io/orchestrator/remix-conventions.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.00184 |
| Opus 5.5 | $0.00000 | $0.00074 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
remix-conventions 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
Frontend Conventions (Optional)
Only apply these rules if the project has a TypeScript/React frontend under portal/.
General
- Keep routes/pages thin; move logic into
portal/src/liborportal/src/services. - Prefer explicit typing at API boundaries.
- Centralize network calls in a small API client module (do not scatter
fetch()). - Treat UI state changes as data-flow: inputs -> validation -> action -> result.
Testing
- Unit tests for pure functions and components with complex logic.
- E2E tests only for critical user journeys (few, stable).
Error Handling
- Show user-safe errors in UI.
- Log developer-facing details in console only for dev builds.
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 · 28 lines · 0 tokens per session scan A 9d7cec5e045a
remix-conventions is a cursor rule published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 184 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-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.
hatch3r-rust-patterns
Rust conventions covering 2024 edition idioms, error handling with thiserror/anyhow, ownership patterns, async with Tokio, testing, and Cargo workspaces.
rust-conventions
rust-conventions.
rust
Rust coding conventions for ralph-core and src-tauri.
rust
Rust patterns: ownership, Result types, iterators.