What is ultra-deliver?

A command for preparing a software project for release after its tests pass. It updates project records, creates a production build, changes the version, and prepares the release in the code repository.

Use it to update a changelog and README, create a production build, generate a technical-debt report, bump the version, create a release tag, and push changes.

It gathers the routine release work into one tracked process, reducing the chance of forgetting documentation, versioning, or build steps. It also checks the project before actions that publish changes.

ultra-deliver — Command for Claude Code by rocky2431/ultra-builder-pro

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.

Clone the repo

git clone --depth 1 https://github.com/rocky2431/ultra-builder-pro

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-deliver/github.svg)](https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-deliver)

Your own site

<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-deliver"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-deliver/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-deliver"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-deliver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,722 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01722
Opus 5.5	$0.00004	$0.00689
Sonnet 5.5	$0.00002	$0.00344
Haiku 4.5	$0.00001	$0.00172

Measured 2mo ago against content hash d15bba71d7e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ultra-deliver 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 2mo 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.

commands/ultra-deliver.md · 197 lines

How it starts

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

/ultra-deliver

Workflow Tracking (MANDATORY)

On command start, create tasks for each major step using TaskCreate:

Step	Subject	activeForm
0.1	Validate /ultra-test Passed	Validating test results...
0.2	Check Uncommitted Changes	Checking git status...
1	Documentation Update	Updating documentation...
1.1	Update CHANGELOG.md	Updating changelog...
1.2	Generate Technical Debt Report	Generating debt report...
1.3	Update README.md	Updating readme...
2	Production Build	Building for production...
3	Version & Release	Bumping version and tagging...
4	Persist Results	Persisting delivery report...

Before each step: TaskUpdate → status: "in_progress" After each step: TaskUpdate → status: "completed" On context recovery: TaskList → resume from last incomplete step

Prepare release after /ultra-test passes: update documentation, build, bump version, tag, and push.

Pre-Delivery Validations (v7 — advisory + user decision)

v7 change: validations surface state and recommend; the user decides. Only irreversible operations (real git push, real publish, real release tag) hard-block.

Validation 1: /ultra-test Passed

Read .ultra/test-report.json and report:

File exists? (if not: "Run /ultra-test first" — recommended, not blocking)
passed is true? (if not: list blocking_issues)
git_commit matches current HEAD? (if not: "Code changed since last test")

If anything fails, use AskUserQuestion with <ask_user_format>:

Re-ground: which validation(s) failed
Recommend: re-run /ultra-test before delivering
Options: A) Re-run /ultra-test now, B) Proceed anyway and accept risk (records gap), C) Cancel delivery

Validation 2: No Uncommitted Changes

Run git status and verify working directory is clean.

If unclean:

Use AskUserQuestion to confirm:
- Option A: "Auto-commit all changes" → commit with chore: pre-delivery cleanup
- Option B: "Review changes first" → show git diff --stat and ask again
- Option C: "Block delivery" → stop and let user handle manually
If user approves commit but it fails (conflicts, etc.) → block and report

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

2mo ago First seen · 197 lines · 11 tokens per session scan A d15bba71d7e3

Subscribe to this mod's changes

ultra-deliver is a command published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 1,722 once invoked, about $0.0000 per session on Opus 5.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-30.

Git and workflow Releases

ultra-deliver next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ultra-deliverrocky2431/ultra-builder-pro	Command	11	3mo ago	MIT	A	11	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	2d ago	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
release-managerruvnet/agentic-flow	Command	838	yesterday	none	A	0	Claude Code
create-prdsswift/ion	Command	5	2d ago	MIT	A	28	Claude Code
rally-merge-prddgonzal3/rally	Command	6	3d ago	MIT	A	0	Claude Code