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 skills add GoranErhartic/cursor-development-rules --skill pre-implementation-gategit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWrote 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/skills/goranerhartic/cursor-development-rules/pre-implementation-gate)<a href="https://agentmods.dev/skills/goranerhartic/cursor-development-rules/pre-implementation-gate"><img src="https://agentmods.dev/badge/skills/goranerhartic/cursor-development-rules/pre-implementation-gate/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/skills/goranerhartic/cursor-development-rules/pre-implementation-gate"><img src="https://agentmods.dev/badge/skills/goranerhartic/cursor-development-rules/pre-implementation-gate.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.00078 | $0.01075 |
| Opus 5 | $0.00039 | $0.00537 |
| Sonnet 5 | $0.00016 | $0.00215 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
pre-implementation-gate 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Implementation Gate
Purpose
This skill enforces process over speed. It prevents the agent from jumping straight into coding by requiring rule discovery and loading before the first line of code is written.
The agent's natural bias is to produce output quickly. This gate exists to override that bias. A detailed user spec defines WHAT to build — rules define HOW to build it. Both are required.
When This Skill Activates
Any request that will result in code changes:
- "implement this plan"
- "build feature X"
- "create a new module"
- "fix this bug"
- "refactor this code"
- Any variation of the above
Gate Checklist
Copy this checklist and complete every step before writing code:
Pre-Implementation Gate:
- [ ] Step 1: project-context.mdc verified (populated, not placeholder)
- [ ] Step 2: Stack router loaded and read
- [ ] Step 3: 2–3 task-relevant rules loaded and read
- [ ] Step 4: development/code-implementation.mdc read
- [ ] Step 5: development/tdd-workflow.mdc read
- [ ] Step 6: Rules declared in response to user
Step-by-Step Procedure
Step 1 — Verify Project Context
Read the file at the path for project-context.mdc in the .cursor/rules/ directory.
If populated: Extract the directory→router mapping. Proceed to Step 2.
If placeholder or missing: STOP. Tell the user:
"Project context is not configured. I need to run project onboarding before I can implement. This analyzes the repo and maps it to the correct rules."
Then read development/project-onboarding.mdc and follow the onboarding procedure. Only proceed after project-context.mdc is written with real values.
Step 2 — Load Stack Router
From the Active Stacks table in project-context.mdc, identify which router file matches the directories you will be touching.
Read that router file. It contains:
- The technology stack summary
- A task→rule mapping table
- Key conventions
Step 3 — Load Task-Relevant Rules
Using the router's task→rule mapping, select 2–3 rules most relevant to the current sub-task. Read each one.
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.
- 11d ago First seen · 121 lines · 78 tokens per session scan A 5267d408d881
pre-implementation-gate is a skill published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 78 tokens to every session and 1,075 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…