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/coddy-project/coddy-agent/implementation-ordergit clone --depth 1 https://github.com/coddy-project/coddy-agentWhat 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.00254 |
| Opus 5 | $0.00000 | $0.00127 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
implementation-order 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 2d 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
Implementation order
For new behavior, workflow.mdc wins on red-green order. Use this file to decide where code lives and which layer to extend first.
- Extend the lowest layer that can own the change with no new upward dependencies.
- Add tests at that layer before or with the change (see
testing.mdc). - Wire through
internal/agentorinternal/acponly after lower pieces exist and pass tests. - Optional HTTP surface - last mile in
external/httpserver, then refreshopenapi.goand docs perapi-layer.mdcandworkflow.mdc.
Forbidden
- Skipping tests for new behavior.
- Placing domain logic in
cmd/or duplicating it in HTTP handlers instead of reusinginternal/APIs.
References
@architecture.mdc @workflow.mdc @api-layer.mdc
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A 39942dc8699d
implementation-order is a cursor rule published in the GitHub repository coddy-project/coddy-agent (127 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 254 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
lean
The smallest working change. Efficiency is not carelessness. Active during delivery in the aiops bundle; off during grill/alignment.
use-bun-instead-of-node-vite-npm-pnpm
../../CLAUDE.md.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.