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.
npx skills add markmhendrickson/neotoma --skill create_releasegit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/neotoma/create_release)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/create_release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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/neotoma/create_release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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.00006 | $0.03946 |
| Opus 5.5 | $0.00002 | $0.01578 |
| Sonnet 5.5 | $0.00001 | $0.00789 |
| Haiku 4.5 | $0.00001 | $0.00395 |
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
95% identical to create-release — 14 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 — 442 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 .claude/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 .claude/skills/ 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 · 442 lines · 6 tokens per session scan A 90fad2af8dd9
create_release is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 3,946 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to create-release, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.