development-process

A set of mandatory rules for an agent-led software development process. It covers analysing a feature, designing its structure, breaking work into tasks, developing with a group of agents, and reviewing the result.

In plain words
What is it for?
Use it to organise feature work from initial analysis through architecture, task planning, team-based implementation, and review.
Why use it?
It gives coding agents a defined sequence for handling larger changes, so important planning and review steps are less likely to be skipped.

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/vepo/contraponto/development-process
Clone the repo
git clone --depth 1 https://github.com/vepo/contraponto

Made for: Cursor.

Per session 4,192 This file is loaded in full into every session.
When invoked 4,192 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.04192 $0.04192
Opus 5 $0.02096 $0.02096
Sonnet 5 $0.00838 $0.00838
Haiku 4.5 $0.00419 $0.00419

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

Security

Grade A, and why

development-process 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.

.cursor/rules/development-process.mdc · 291 lines

The source is not reproduced here

Licensed GPL-2.0

The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 291 lines · 4,192 tokens per session scan A 197e8c2a818f

Subscribe to this mod's changes

development-process is a cursor rule published in the GitHub repository vepo/contraponto (2 stars, last pushed 22d ago), licensed GPL-2.0. It adds 4,192 tokens to every session, about $0.0210 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.