evolving-conventions

A project-maintenance rule that keeps shared coding practices written down as the project changes. It covers files such as rules, skills, and the README, which explains setup and maintenance to people and coding agents.

In plain words
What is it for?
Use it when introducing or changing a project-wide convention, requirement, or repeatable workflow. It helps decide whether to update an existing rule or skill, create a new one, or revise the README.
Why use it?
It prevents important decisions about file layout, naming, testing, and tools from existing only in code or in someone's memory. It also helps keep guidance for existing and new code consistent.

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/kws-projects/react-boilerplate/evolving-conventions
Clone the repo
git clone --depth 1 https://github.com/kws-projects/react-boilerplate

Made for: Cursor.

Per session 323 This file is loaded in full into every session.
When invoked 323 The same file — it is already loaded in full.
Security scan A 0 findings. 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.00323 $0.00323
Opus 5 $0.00161 $0.00161
Sonnet 5 $0.00065 $0.00065
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

evolving-conventions 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/evolving-conventions.mdc · 35 lines

What it actually says

Evolving Conventions

When a new project-wide convention, requirement, or recurring pattern is introduced or changed (e.g. file layout, naming, testing, tooling, integration patterns), update the documentation in the same change - do not leave it implicit in code only.

What to update

  • .cursor/rules/ - update the relevant rule (e.g. project-structure, best-practices, maintaining-boilerplate) so future agents follow it.
  • .cursor/skills/ - update the relevant skill, or add a new one when a workflow is involved (multi-step, repeatable, or with gotchas).
  • README.md - update if the change affects how a human sets up, runs, or maintains the project.

When to create a new rule or skill

Prefer editing an existing rule/skill. Create a new one only when it clearly improves readability or management - i.e. the topic is self-contained and would bloat or muddy an existing file. Keep each rule focused and concise; keep skills action-oriented with clear steps.

Consistency

  • Apply the new convention to existing code where reasonable, not just new code.
  • Keep rules, skills, and README in agreement; if they conflict, fix all of them.
  • Avoid duplicating the same guidance across files - state it once and reference it (e.g. point to a skill from a rule).
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 · 35 lines · 323 tokens per session scan A f003550e52a4

Subscribe to this mod's changes

evolving-conventions is a cursor rule published in the GitHub repository kws-projects/react-boilerplate (3 stars, last pushed 2mo ago), licensed MIT. It adds 323 tokens to every session, about $0.0016 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.