A command that breaks a large task into smaller jobs and coordinates multiple agents working on them in parallel. It also tracks communication, progress, reviews, and shared learnings.

Use it to plan subtasks, assign work, monitor agents, review their changes, mark tasks complete, and save useful results for later work.

It helps divide complex work clearly and makes it easier to see what each worker is doing or where one is blocked.

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

Your own site

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

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

When invoked 781 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.00010	$0.00781
Opus 5.5	$0.00004	$0.00312
Sonnet 5.5	$0.00002	$0.00156
Haiku 4.5	$0.00001	$0.00078

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

Security

Grade A, and why

forge 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 8d 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/forge.md · 59 lines

How it starts

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

Decompose a task and spawn parallel workers.

Critical Invariants

These rules are non-negotiable and MUST NOT be skipped:

Review MUST complete before marking work done — step 7 (review) MUST finish before step 8 (complete). NEVER skip review.
The review gate is mandatory — forge_complete MUST NOT be called until forge_review has passed for every worker. NEVER bypass the review gate.
ALWAYS create a forge, even for small tasks.
Coordinator orchestrates, workers execute — workers MUST NOT call forge_complete.

Task

$ARGUMENTS

Workflow

Initialize comms: comms_init(project_path=".", task_description="Forge: <task>")
Check prior learnings: hivemind_find(query="<task keywords>")
Decompose: forge_decompose(task="<task>", context="<learnings>")
- Before decomposing, check historical success rates: forge_get_strategy_insights(task="<task>")
- Choose from: file-based, feature-based, risk-based, or auto
Create epic: org_create_epic(epic_title="<task>", subtasks=[...])
For each subtask: forge_spawn_subtask(bead_id, epic_id, subtask_title, files, task_classification, skill | skill_absent_reason)
- task_classification is required: deterministic or judgment
- deterministic subtasks require a skill reference (verified skill name or repo-relative script path) OR a skill_absent_reason — never both
- judgment subtasks must omit both skill and skill_absent_reason — supplying either fails input validation
- Unverifiable references fail closed (SKILL_NOT_FOUND); missing both fails with SKILL_REFERENCE_REQUIRED
- Pass project_path when spawning against a repo other than the current directory
- Forward the envelope's skill_directive verbatim into the worker prompt (or pass the same skill to forge_subtask_prompt); never write skill instructions yourself
Monitor: check comms_inbox() every few minutes
- comms_inbox() — check for messages from workers
- forge_status(epic_id, project_key) — check worker progress
- org_cells(status="in_progress") — see active cells
- If a worker is blocked: read the message with comms_read_message(message_id), acknowledge with comms_ack(message_id), then either unblock or reassign the subtask
Review FIRST (before complete): forge_review(task_id, files_touched) for each completed worker — MUST finish before step 8
Complete (after ALL reviews pass):
- forge_complete(bead_id, summary, files_touched) — mark epic done
- forge_record_outcome(bead_id, duration_ms, success) — record for learning
- hivemind_store(information="...", tags="forge,<topic>") — store learnings
- org_sync() — persist state to git

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

8d ago Changed · -9 lines 5bd7fb116aa0
2mo ago First seen · 68 lines · 10 tokens per session scan A 336fc4a6d56b

Subscribe to this mod's changes

forge is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 781 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-31.

Building agents Planning

forge next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
forgeunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	10	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