Borrowing it
Nothing to install: this file belongs to markmhendrickson/foundation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/markmhendrickson/foundation/main/.cursor/skills/create-release/SKILL.mdgit clone --depth 1 https://github.com/markmhendrickson/foundationWrote 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.
[](https://agentmods.dev/skills/markmhendrickson/foundation/create-release)<a href="https://agentmods.dev/skills/markmhendrickson/foundation/create-release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/create-release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00017 | $0.03969 |
| Opus 5.5 | $0.00007 | $0.01588 |
| Sonnet 5.5 | $0.00003 | $0.00794 |
| Haiku 4.5 | $0.00002 | $0.00397 |
Grade A, and why
create-release 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 1mo 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.
This is a copy
98% identical to create-release — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Release
Orchestrates multiple Feature Units into a cohesive release. Implements the Release workflow from foundation/development/release_workflow.md.
When to Use
Explicit Command: Use when you know exactly what you want: start a new release, plan multi-FU work with dependency resolution, generate execution schedules with parallelization, orchestrate FU creation/execution in dependency order, run cross-FU integration tests.
Automatic Detection: This workflow can also be triggered automatically via .cursor/rules/release_detection.md when you mention release-related patterns in natural language (e.g., "new release", "release v1.1.0"). Both paths execute the same workflow.
This is a foundation command. If installed, it will be available in .cursor/commands/ via symlink.
Prerequisites
- Release ID chosen (format:
vX.Y.Z, e.g.,v1.0.0) - Release scope roughly defined (what's in, what's out)
- FU IDs for included work identified (or to be created)
Command Execution
Step 1: Load Documentation
Load required documents:
foundation/development/release_workflow.md(primary workflow)docs/feature_units/standards/creating_feature_units.md(FU creation)docs/feature_units/standards/execution_instructions.md(FU execution)docs/feature_units/completed/anddocs/feature_units/in_progress/(for Feature Unit specs)
Step 2: Checkpoint 0 — Release Planning
Check if Release plan exists:
- Look for
docs/releases/in_progress/{release_id}/release_plan.md - Look for
docs/releases/in_progress/{release_id}/manifest.yaml
If Release plan exists: Load and validate. If complete → proceed to Step 3. If incomplete → prompt user to complete.
If Release plan does NOT exist: Prompt user interactively for Release details:
- Release name and version (e.g., "MVP", "v1.0.0")
- Release goal (1-2 sentence summary of what this ships)
- Target ship date (date or "when ready")
- Priority (P0 critical / P1 high / P2 normal)
- Included Feature Units (list of FU IDs, e.g., "FU-100, FU-101, FU-102")
- Excluded scope (what's explicitly NOT in this release)
- Release-level acceptance criteria:
- Product acceptance (core workflows, empty/error states)
- Technical acceptance (test coverage, performance, integrity)
- Business acceptance (metrics, KPIs)
- Cross-FU integration test requirements (flows that span multiple FUs)
- Deployment strategy (staging_first / canary / full_rollout)
- Rollback plan (how to revert if issues found)
- Post-release monitoring plan (key metrics, alerts)
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.
- 1mo ago First seen · 445 lines · 17 tokens per session scan A 8bcf39d44b00
create-release is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 3,969 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to create-release, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.