writing_code_protocol

Rules for organizing and writing code in a software project. They cover where tests and implementations go, how files are exported, and how application state is accessed.

In plain words
What is it for?
Use them when adding files, locating implementations, exporting modules, subscribing to observable state, choosing enums, or defining value-comparable classes.
Why use it?
They give developers consistent places and patterns for related code, making implementations easier to find and maintain. They also discourage fragile string-based code.

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/arenukvern/mcp_flutter/writing_code_protocol
Clone the repo
git clone --depth 1 https://github.com/Arenukvern/mcp_flutter

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 124 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00124
Opus 5 $0.00000 $0.00062
Sonnet 5 $0.00000 $0.00025
Haiku 4.5 $0.00000 $0.00012

Measured 2d ago against content hash 0232d007f2cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

writing_code_protocol 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.

.cursor/rules/writing_code_protocol.mdc · 16 lines

What it actually says

Writing Code Protocol

  • Place mock, test and implementation exactly near intent file.
  • Export files from its folders using barrel file (ui/ui.dart, commands/commands.dart etc.).
  • To find implementation, try to load intents first.
  • Do not rely on strings, use enums.
  • Use context.read/context.select to subscribe to observable state in build methods.
  • If you create new file, make sure to check its intent. If it doesn't have an intent - create it.
  • Use EquatableMixin for classes.
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. 2d ago First seen · 16 lines · 124 tokens per session scan A 0232d007f2cb

Subscribe to this mod's changes

writing_code_protocol is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (370 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 124 tokens. 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.