A command that runs an end-to-end software change workflow for Speckit or OpenSpec, from clarifying the idea and writing the plan through implementation, review, and demo instructions.

Use it to take a specification from an early draft to demo-ready code, including task generation, specification review, implementation, code review, and retrospective notes.

It coordinates the repeated planning and review steps and can resume from recorded progress when human judgment is needed.

How unbound-force/gaze configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/commands/uf.unleash.md

Clone the repo

git clone --depth 1 https://github.com/unbound-force/gaze

Made for: Claude Code, OpenCode.

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/unbound-force/gaze/uf.unleash/github.svg)](https://agentmods.dev/commands/unbound-force/gaze/uf.unleash)

Your own site

<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.unleash"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.unleash/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/unbound-force/gaze/uf.unleash"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.unleash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 18,902 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.00087	$0.18902
Opus 5.5	$0.00035	$0.07561
Sonnet 5.5	$0.00017	$0.03780
Haiku 4.5	$0.00009	$0.01890

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

Security

Grade A, and why

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

.opencode/commands/uf.unleash.md · 1,994 lines

How it starts

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

Command: /uf.unleash

Description

Autonomous pipeline execution for Speckit (strategic), OpenSpec (tactical), and quick (trivial) changes. When no spec exists yet (main or an unrecognized branch), tier routing selects the workflow first, starts it, and takes the change from description to demo-ready code in a single command. Orchestrates 8 steps: clarify, plan, tasks, spec review, implement, code review, retrospective, and demo. Exits gracefully when human judgment is needed and resumes from where it left off on re-run.

Usage

/uf.unleash [change description]

The optional description argument ($ARGUMENTS) is consumed only by tier routing (Step 1a), when the branch gate reports ON_MAIN or UNRECOGNIZED_BRANCH; on a tier branch it is ignored — the existing change drives the pipeline. The description may be plain text or a GitHub issue reference (#NNN or an issues URL), which the tier-routing skill resolves.

Instructions

SESSION-RESUME GUARD (re-anchor rule): After ANY context compression (auto-compaction, the compress tool) or a session restart, do NOT infer progress from the compression summary. Re-anchor on durable state instead:

Call get_progress with command: "uf.unleash". Its completed_steps and phases records are authoritative.

Call parse_tasks on the feature dir's tasks.md (speckit and openspec tiers). Checked boxes are authoritative.

Where the compression summary disagrees with either result, the durable tool result wins.

NEVER re-run a phase pre-flight checkpoint whose phases["<N>"].verdict is "green" — continue with the next incomplete task or phase.

NEVER re-verify a task parse_tasks reports done. mark_task_complete is idempotent — a duplicate call is safe; re-doing completed work is not.

At pipeline start (before Step 0), only the uf_unleash_detect_resume result (checkpoint state plus dispatch artifacts, with artifact evidence authoritative) determines resumability.

Read the full file on GitHub · 1,994 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 Changed · +32 lines c872a7d1562e
3d ago Changed · +85 lines 6527d7bcaa4c
8d ago Changed · +1,103 lines · +27 tokens per session 62d2d319ffcb
1mo ago Changed b64fe037c45d
2mo ago Changed · +33 lines 5a3663ee81c1
2mo ago First seen · 741 lines · 60 tokens per session scan A 2ee13399d1fd

Subscribe to this mod's changes

uf.unleash is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 87 tokens to every session and 18,902 once invoked, about $0.0003 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-31.

Building agents Planning

uf.unleash next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
uf.unleashunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	87	Claude Code, OpenCode
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

gaze: Command for Claude Code