agentmods.dev

release-discipline

release-discipline is a cursor rule for Cursor from arturogarrido/claudinho. It costs 540 tokens per session, scanned A, original, MIT.

A set of rules for grouping changes into releases, keeping private files out of public history, and running checks before publishing a package.

In plain words
What is it for?
Use it when preparing a release, reviewing the final difference from the main branch, checking release quality, and recording AI-assisted commit attribution.
Why use it?
It reduces accidental releases of unfinished code or internal documents and keeps related fixes together.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

not rated 28repo yesterday A scan 540 tokens original MIT

Good fit Use it when preparing a release, reviewing the final difference from the main branch, checking release quality, and recording AI-assisted commit attribution.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/arturogarrido/claudinho/release-discipline
View source ↗ arturogarrido/claudinho npmjs.com
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.

Clone the repo
git clone --depth 1 https://github.com/arturogarrido/claudinho

Made for: Cursor.

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

agentmods badge for release-discipline

README.md
[![agentmods](https://agentmods.dev/badge/rules/arturogarrido/claudinho/release-discipline.svg)](https://agentmods.dev/rules/arturogarrido/claudinho/release-discipline)
Your own site
<a href="https://agentmods.dev/rules/arturogarrido/claudinho/release-discipline"><img src="https://agentmods.dev/badge/rules/arturogarrido/claudinho/release-discipline.svg" alt="Measured on agentmods" height="20"></a>
Per session 540 This file is loaded in full into every session.
When invoked 540 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00540 $0.00540
Opus 5 $0.00270 $0.00270
Sonnet 5 $0.00108 $0.00108
Haiku 4.5 $0.00054 $0.00054

Measured 8d ago against content hash 07bbb185e4a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

release-discipline 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 8d 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/release-discipline.mdc · 36 lines

What it actually says

Release discipline

One feature, one release

  • One user-facing feature → one minor. Stack review fixes (tz, dates, guards) into the same PR before merge when they belong to the same feature.
  • Do not tag npm until CI is green and pnpm release:qa passes (tripwires at the end must be 0 failed).
  • Before tagging: git diff main must not include accidental private paths (docs/, CLAUDE.local.md, .env).

Commit attribution

Every commit produced with an AI agent: follow AGENTS.md § Commit attribution — trailer names the agent and model in use (e.g. Co-Authored-By: Cursor (Composer 2.5) <[email protected]>).

Public vs private docs

Tracked (public engineering guides): AGENTS.md, CLAUDE.md, .cursor/rules/, README, MCP tool descriptions.

Gitignored (maintainer-local): docs/ (e.g. docs/AGENTS.internal.md notebook), CLAUDE.local.md.

  • Engineering process → update the public guides above.
  • Candid history, strategy, or release post-mortems → docs/ notebook only.
  • Never add !docs/… exceptions to .gitignore without explicit maintainer approval.

Bracket / live-formatting ship checklist

Before merge or release of bracket or kickoff-formatting work:

  1. Adversarial tests: 0 games, mid-tournament (2/3 played), degraded standings.
  2. Surface parity: CLI bracket + MCP get_bracket + share bracket all pass tz and show calendar dates on multi-week knockouts.
  3. Statusline knockouts (if touched): indirect-resolve via cached getKnockoutFixtures — hot path fail-closed (no 🏳️ on countdown or live · syncing…); empty-cache short TTL; knockout-surface-coverage.test.ts + statusline.test.ts / refresh.test.ts green. See .cursor/rules/surface-parity.mdc.
  4. After pnpm -r build, run pnpm release:qa and eyeball the rendered sections; keep packages/mcp/test/tools.test.ts green for MCP arg threading.
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. 8d ago First seen · 36 lines · 540 tokens per session scan A 07bbb185e4a7

Subscribe to this mod's changes

release-discipline is a cursor rule published in the GitHub repository arturogarrido/claudinho (28 stars, last pushed yesterday), licensed MIT. It adds 540 tokens to every session, about $0.0027 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-30.

Claude CodeGit and workflowReleasesclifootballfutbollive-scoresmcp
Related

Other cursor rules, from other repositories

hatch3r-git-conventions

Conventional Commits type list, subject line rules, breaking-change footer format, branch naming template for type/short-description, and change-size discipline (PR-size ceiling with stacked-change escape hatch).

hatch3r/hatch3r · 39 tokens

release-changelog

Keep a Changelog and semver steps when cutting dbt-doctor releases.

northgraindata/dbt-doctor · 0 tokens

changelog

Changelog and release notes rules.

Pranav-Karra-3301/tuck · 0 tokens

release-checklist

What to update with each code change or version release.

yoreai/relay · 215 tokens

release-policy

Release, versioning, and signing policy for setmac.

v0id-user/setmac · 238 tokens

sciclaw-papercuts

Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.

sciclaw/sciclaw · 607 tokens