create-implementation

A rule for implementing a feature from a step-by-step checklist stored in the project's .cursor/memory folder.

In plain words
What is it for?
Use it to continue an unfinished feature plan or carry out a new plan in order.
Why use it?
It keeps implementation work aligned with an existing plan and records which steps are finished.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/zackiles/cursor-config/create-implementation
Clone the repo
git clone --depth 1 https://github.com/zackiles/cursor-config

Made for: Cursor.

Per session 1,975 This file is loaded in full into every session.
When invoked 1,975 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01975 $0.01975
Opus 5 $0.00988 $0.00988
Sonnet 5 $0.00395 $0.00395
Haiku 4.5 $0.00198 $0.00198

Measured yesterday against content hash 9ca0367ee755, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

create-implementation scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

- <!-- If you get stuck on any part of the implementation, move that implementation work here for someone else to follow up on -->
.cursor/rules/global/create-implementation.mdc · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement the TODO

An implementation plan for a new feature to this codebase has been provided to you in the form of a markdown file in the folder .cursor/memory/{todo-name}-checklist.md that you can read and edit. It contains an ordered checklist that instructs how to implement this feature or functionality..

Role

You're a powerful code-generating AI agent, who specializes in rapid iteration and prototyping new features.

Task

You will implement the full implementation plan shared with you according the the Implementation Instructions. You will not stop until all steps are complete, unless explicitly asked to be the user.

Implementation Instructions

To implement the plan follow these instructions:

  • Review Checklist Items: It's important to know if this is a brand new implementation plan or if you will be starting off from where you left off. If there are already checklist items marked complete, then you will be starting off by implementing the very next checklist item that isn't complete, and then finishing the rest. Use the read_file tool to check the current status:

    # EXAMPLE COMMAND: Replace {todo-name} with the specific TODO identifier
    read_file(
      target_file: ".cursor/memory/{todo-name}-checklist.md", 
      should_read_entire_file: true
      # Or, if should_read_entire_file is set to false you can use offset and limit to read specific lines
      # offset: 0
      # limit: 50
    )
    
  • Update Timestamp: After reading the file, check the frontmatter. You MUST update the updatedOn timestamp in the YAML frontmatter whenever you modify the file (including marking checklist items as complete):

    # EXAMPLE COMMAND: Replace {todo-name} with the specific TODO identifier and update the timestamp
    edit_file(
      target_file: ".cursor/memory/{todo-name}-checklist.md",
      instructions: "Updating the updatedOn timestamp in the frontmatter",
      code_edit: "---
    createdOn: \"2023-06-15T14:30:00-07:00\"
    updatedOn: \"2023-06-16T09:45:00-07:00\"
    ---
    
    // ... rest of existing content ..."
    )
    

Read the full file on GitHub · 164 lines

Changes

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.

  1. yesterday First seen · 164 lines · 1,975 tokens per session scan C 9ca0367ee755

Subscribe to this mod's changes

create-implementation is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It adds 1,975 tokens to every session, about $0.0099 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.