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 rules/coeusyk/inference-x/planninggit clone --depth 1 https://github.com/coeusyk/inference-xWhat 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.00219 | $0.00219 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
planning 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 yesterday.
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
Planning rules
- For any task beyond a small localized edit, write a short execution plan first.
- The plan must include: goal, affected files, ordered steps, and validation approach.
- Group edits by concern: schemas, services, routes, tests, docs.
- Complete one concern before moving to the next when possible.
- If a task touches contracts, docs and tests must be updated in the same work batch.
- Prefer finishing a thin vertical slice over partially scaffolding many modules.
Phase discipline
- Follow
docs/PHASES.mdas the default execution order. - Do not start a later phase before the current phase exit criteria are met unless explicitly instructed.
- Record architectural changes in
docs/DECISIONS.mdwhen a non-obvious design choice is made.
Implementation rhythm
- Read relevant architecture and phase docs.
- Restate the task in repo terms.
- Propose the file-level plan.
- Implement in small steps.
- Validate with tests or smoke checks.
- Update docs affected by the change.
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.
- yesterday First seen · 24 lines · 219 tokens per session scan A d78c127c7add
planning is a cursor rule published in the GitHub repository coeusyk/inference-x (2 stars, last pushed 21d ago), licensed MIT. It adds 219 tokens to every session, about $0.0011 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.