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.
curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/commands/uf.unleash.mdgit clone --depth 1 https://github.com/unbound-force/gazeWrote 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/commands/unbound-force/gaze/uf.unleash)<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.
<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>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.00060 | $0.06345 |
| Opus 5 | $0.00030 | $0.03173 |
| Sonnet 5 | $0.00012 | $0.01269 |
| Haiku 4.5 | $0.00006 | $0.00634 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 774 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 both Speckit (strategic) and OpenSpec (tactical) changes. Takes a spec from draft 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
Instructions
SESSION-RESUME GUARD: If you are resuming this command after context compression or a session restart, STOP and re-read this entire template before continuing. Do NOT infer which steps are complete from compressed context summaries. Only filesystem markers are authoritative for resumability:
- Task checkboxes (
[x]vs[ ]) intasks.md<!-- spec-review: passed -->intasks.md<!-- code-review: passed -->intasks.mdMaintain the execution checklist below using the Edit tool. Update it in-place as each step, phase, or iteration completes. This is your live state record.
Execution Checklist -- update in-place with Edit tool:
- [ ] Step 0: Startup Cleanup
- [ ] Step 1: Branch Safety Gate
- [ ] Step 2: Resumability Detection
- [ ] Step 3: Clarify (Step 1)
- [ ] Step 4: Plan (Step 2)
- [ ] Step 5: Tasks (Step 3)
- [ ] Step 6: Spec Review (Step 4) -- iteration: 0/3
- [ ] Step 7: Implement (Step 5) -- phase: 0/N, batch: 0/N, workers: 0/N
- [ ] Step 8: Code Review (Step 6) -- iteration: 0/3
- [ ] Step 9: Retrospective (Step 7)
- [ ] Step 10: Demo (Step 8)
0. Startup Cleanup
Before any pipeline logic, clean up stale worktrees from previous interrupted runs:
- Call
swarm_worktree_listwith the project path. - If any worktrees exist, call
swarm_worktree_cleanupwithcleanup_all: trueto remove them. - This cleanup does NOT affect resumability -- spec.md, plan.md, tasks.md, and task checkboxes live in the main working directory, not in worktrees.
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.
- 5d ago Changed · +33 lines 5a3663ee81c1
- 9d ago First seen · 741 lines · 60 tokens per session scan A 2ee13399d1fd
uf.unleash is a command published in the GitHub repository unbound-force/gaze (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 60 tokens to every session and 6,345 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.