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/goranerhartic/cursor-development-rules/code-implementationgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWhat 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.00025 | $0.00315 |
| Opus 5 | $0.00013 | $0.00158 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
code-implementation 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
Code Implementation Workflow
When implementing features, refactoring code, or fixing bugs, you must adhere to the following workflow and checklists.
Workflow Steps
1. Pre-Work
Before writing code:
- Clarify any ambiguous requirements.
- Identify existing patterns in the codebase to replicate.
- Verify required dependencies are available.
2. Implementation (TDD Cycle)
- Write failing test first that defines the expected behavior
- Implement minimum code to make the test pass
- Refactor while tests remain green
- Repeat for each behavior unit
Exception: Trivial changes may skip TDD only under the criteria in
development/tdd-workflow.mdc, with documented justification.
3. Verification (Definition of Done)
Before marking the task as complete, ensure:
- Project builds successfully
- All tests pass
- No secrets exposed
- Input sanitization at boundaries
- Follows existing patterns
- Error handling implemented
Summary Requirement
Every implementation task must conclude with a summary in the following format:
- What changed
- Why
- How to verify
- Limitations
See also: development/tdd-planning.mdc, development/tdd-workflow.mdc, development/code-review.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 · 42 lines · 25 tokens per session scan A 88a5908bb2f7
code-implementation is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 315 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
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.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.