What is create-release?

A workflow for planning and creating a software release, meaning a named version of a product or codebase that is prepared for delivery. It identifies the release scope, version, type, and configured storage location before proceeding.

Use it when starting a release, planning a version such as v1.0.0, deciding which features belong in it, or organizing an internal or external release.

It gives release work a defined plan and schedule instead of leaving features and timing scattered across discussions. It also checks the project's release settings before creating files or records.

create-release — Skill 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 skills/markmhendrickson/ateles/create-release

Any agent

npx skills add markmhendrickson/ateles --skill create-release

Clone the repo

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

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 862 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.00062	$0.00862
Opus 5	$0.00031	$0.00431
Sonnet 5	$0.00012	$0.00172
Haiku 4.5	$0.00006	$0.00086

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

Security

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

.claude/skills/create-release/SKILL.md · 95 lines

How it starts

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

Create Release

Plan and create a new software release following the release workflow.

When to Use

Use this skill when:

User mentions "new release", "create release", "plan release"
User references version numbers in release context (e.g., "v1.0.0", "v2.0.0")
User asks to "split out features" into a release
Planning discussions about release scope and timeline
User explicitly invokes /create-release

Workflow

Step 1: Detect and Confirm

Identify release intent from user context:
- Extract release ID/version if mentioned (e.g., "v1.0.0")
- Note release type hints (internal/external, marketed/not_marketed)
- Capture scope hints (what features or functionality)
Load configuration:
- Read foundation-config.yaml for release settings
- Check if orchestration.release.enabled is true
- Determine orchestration.release.directory path

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 no release ID detected, ask: "What release ID/version should I use?"

Handle exceptions:
- If user says "just a spec document" → create spec only, not full release
- If user says "no" → do not proceed

Step 2: Execute Release Workflow

If user confirms (yes):

Load required foundation documents:
- foundation/development/release_workflow.md — primary workflow
- foundation/agent_instructions/cursor_commands/create_release.md — command implementation
- foundation/development/feature_unit_workflow.md — if feature units enabled
- Repository-specific execution instructions (if they exist)
Create release structure in {configured_directory}/in_progress/{release_id}/:
- release_plan.md — release goals, scope, out of scope
- manifest.yaml — batches, checkpoints, dependencies
- execution_schedule.md — ordered execution plan
- status.md — current status, batch tracking
- integration_tests.md — if configured
- discovery_plan.yaml — if discovery enabled in config
- participant_recruitment_log.md — if discovery enabled

Read the full file on GitHub · 95 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.

2d ago First seen · 95 lines · 0 tokens per session scan A 0acaa7c59aab

Subscribe to this mod's changes

create-release is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 862 once invoked, about $0.0003 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.

Autonomous Agents Git and workflow LLM Planning Releases aauth agent-swarm ai-agents claude

github

Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.

adolfousier/opencrabs · 65 tokens

publish-harness

Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.

ruvnet/metaharness · 37 tokens

commit-pr

Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…

ZaxbyHub/opencode-swarm · 100 tokens

create-release