What is release_detection?

A rule that detects when a conversation is about creating a software release, such as version 1.1.0.

Recognizing release requests, reading release configuration, collecting version and scope details, and asking for confirmation.

It reduces the chance of missing required release settings, version details, or confirmation before starting the release process.

release_detection — Cursor rule by markmhendrickson

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/markmhendrickson/foundation/release_detection

Clone the repo

git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Cursor.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 805 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.

Model	Per session	Once invoked
Fable 5	$0.00025	$0.00805
Opus 5	$0.00013	$0.00402
Sonnet 5	$0.00005	$0.00161
Haiku 4.5	$0.00003	$0.00081

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

Security

Grade A, and why

release_detection 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/release_detection.mdc · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Detection Rule

Reference: foundation/development/release_workflow.md — "Release Detection" section

Configuration is read from foundation-config.yaml.

Trigger Patterns

When a user mentions any of the following patterns, automatically detect release intent:

"new release"
"internal release"
"create release"
"release vX.Y.Z"
"split out [features] into a [type] release"
"prior release"
"pre-MVP release"
"MCP-focused release"
"v0.X.Y release"
Version numbers in release context (e.g., "v1.1.0", "v2.0.0")
Release-related planning discussions

Agent Actions

Step 1: Detection and Confirmation

If context suggests a release (mentions "release", version numbers, "split out", "prior", etc.):

Load configuration:
- Read foundation-config.yaml to get release settings
- Check if orchestration.release is enabled
- Determine release directory structure
Extract release information from context:
- Release ID/version (if mentioned, e.g., "v1.0.0", "v1.1.0")
- Release type hints (internal/external, marketed/not_marketed)
- Scope hints (what features/FUs are mentioned)

Ask for confirmation:

I see you're requesting a new release. Should I create a release plan in 
`{configured_releases_directory}/in_progress/{release_id}/` following the release workflow? (yes/no)

If release ID was detected, include it in the path.

Exception handling:
- If user explicitly says "just a spec document" or "specification only" → create a spec document instead
- If user says "no" → do not proceed with release creation

Step 2: Execute Release Workflow

If user confirms (yes):

Load required documents:
- foundation/development/release_workflow.md (primary workflow)
- Skill create-release (.cursor/skills/create-release/SKILL.md or foundation/agent_instructions/cursor_skills/create-release/SKILL.md)
- foundation/development/feature_unit_workflow.md (for FU creation, if feature units enabled)
- Repository-specific execution instructions (if they exist)

Read the full file on GitHub · 93 lines

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.

yesterday First seen · 93 lines · 25 tokens per session scan A 73bdd527ff67

Subscribe to this mod's changes

release_detection is a cursor rule published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 805 once invoked, about $0.0001 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.

Git and workflow Productivity

release_detection

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release Detection Rule

Trigger Patterns

Agent Actions

Step 1: Detection and Confirmation

Step 2: Execute Release Workflow

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs