agentmods.dev

create-release

create-release is a skill for Claude Code from markmhendrickson/ateles. It costs 0 tokens per session (862 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
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.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

not rated 5repo today A scan 0 tokens original MIT

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

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markmhendrickson/ateles/create-release
View source ↗ markmhendrickson/ateles
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.

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.

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 create-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/ateles/create-release/github.svg)](https://agentmods.dev/skills/markmhendrickson/ateles/create-release)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/create-release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/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.

agentmods 80×15 button for create-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/create-release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/create-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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. 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.00000 $0.00862
Opus 5.5 $0.00000 $0.00345
Sonnet 5.5 $0.00000 $0.00172
Haiku 4.5 $0.00000 $0.00086

Measured 1mo ago against content hash 0acaa7c59aab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.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

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

  2. Load configuration:

    • Read foundation-config.yaml for release settings
    • Check if orchestration.release.enabled is true
    • Determine orchestration.release.directory path

  3. 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?"

  4. 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):

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

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

  1. 1mo 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 today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 862 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-31.

Autonomous AgentsGit and workflowLLMReleasesaauthagent-swarmai-agentsclaude
Related

Other skills, from other repositories

git-workflow

When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.

0xNyk/oneclaw · 0 tokens

release-prep

Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.

massgen/MassGen · 25 tokens

massgen-release-documenter

Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.

massgen/MassGen · 42 tokens

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

NousResearch/hermes-agent · 19 tokens

otto-drive-pr

PR mergeability, CI, and live preview.

omnigent-ai/omnigent · 14 tokens