What is uf.run-pipeline-plan?

A command that runs a prioritised work plan through a sequence of Unbound Force development steps for each item.

Use it with a plan file or GitHub issue references to track and execute multiple work items through the full pipeline.

It gives each work item the same issue resolution, workflow entry, execution, staging, and commit-approval path while stopping when a required step is paused.

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

Your own site

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

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

When invoked 3,622 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.00050	$0.03622
Opus 5.5	$0.00020	$0.01449
Sonnet 5.5	$0.00010	$0.00724
Haiku 4.5	$0.00005	$0.00362

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

Security

Grade A, and why

uf.run-pipeline-plan 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 3d 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.run-pipeline-plan.md · 379 lines

How it starts

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

Command: /uf.run-pipeline-plan

User Input

$ARGUMENTS

Description

Orchestrate a prioritized work plan through the full Unbound Force pipeline. Each work item is executed through two sequential uf_delegate_command delegations:

Delegation 1 (/uf.unleash): delegated with command_path: ".opencode/commands/uf.unleash.md" and a prompt carrying the work item's description and issue reference(s). The child session resolves the issue, routes the workflow tier, runs the tier's entry command, and executes the pipeline through the demo step.
Delegation 2 (/uf.finale): delegated with command_path: ".opencode/commands/uf.finale.md" and a prompt carrying the work item's context, only after the demo completes. The child session drives staging and commit preparation, then hands off at its commit-approval gate; the human completes the finale interactively.

/uf.unleash paused exits are recognized, relayed verbatim, and block the work item. Progress is tracked per item via todowrite.

Supports two input modes: a plan file path or space- separated GitHub issue references (#NNN or URLs).

Usage

/uf.run-pipeline-plan sprint-42.md
/uf.run-pipeline-plan #123 #456 #789
/uf.run-pipeline-plan https://github.com/unbound-force/unbound-force/issues/42 #99

Instructions

SESSION-RESUME GUARD: When resuming after context compression or a session restart, re-read this entire template before continuing. Compressed context summaries MUST NOT determine item completion. Only todowrite entries and disk state (branches, spec artifacts, PRs) are authoritative for resumability.

Execution Checklist

Maintain this checklist using the todowrite tool: one entry per work item. Entry completion follows the rule in the Tracking section.

Phase 0 — Input Resolution and Confirmation

Phase 0 runs in the orchestrator context (no subagents).

Detect input type: Determine whether $ARGUMENTS is an existing file path.
- File path: PROCEED to the Parse Plan File step.
- Otherwise: PROCEED to the Resolve Issue Metadata step. Treat the input as space-separated GitHub issue references (#NNN or full GitHub URLs).

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

3d ago Changed · +10 lines 0e2403e940aa
8d ago First seen · 369 lines · 50 tokens per session scan A b141af67ae99

Subscribe to this mod's changes

uf.run-pipeline-plan is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 3,622 once invoked, about $0.0002 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-10-29.

Planning Project management

uf.run-pipeline-plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
uf.run-pipeline-planunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	50	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