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.cobalt-crush.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.cobalt-crush)<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.cobalt-crush"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.cobalt-crush/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.cobalt-crush"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.cobalt-crush.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.00045 | $0.00999 |
| Opus 5 | $0.00023 | $0.00500 |
| Sonnet 5 | $0.00009 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
uf.cobalt-crush 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 10d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: /uf.cobalt-crush
Description
Invoke the Cobalt-Crush developer persona to implement code with clean code principles, convention pack adherence, and feedback loop integration.
User Input
$ARGUMENTS
Usage
/uf.cobalt-crush [task description or instructions]
/uf.cobalt-crush # auto-detect workflow and implement
Examples
/uf.cobalt-crush implement T015 from tasks.md
/uf.cobalt-crush fix the failing test in internal/metrics/store_test.go
/uf.cobalt-crush refactor runMetrics to reduce complexity
/uf.cobalt-crush # detects speckit or openspec context
Instructions
When arguments are provided
Delegate to the cobalt-crush-dev agent using the Task tool with
subagent_type: "cobalt-crush-dev". Pass the user's arguments as
the task prompt. The agent will:
- Read AGENTS.md, constitution, convention packs, and active specs
- Apply its engineering philosophy (clean code, SOLID, TDD awareness)
- Load convention packs from
.opencode/uf/packs/ - Check
.uf/artifacts/for Gaze/Divisor feedback - Execute the requested task following project conventions
- Document design decisions in code comments
When no arguments are provided
Detect the active workflow and delegate the corresponding
implementation command to the cobalt-crush-dev agent:
-
Check for a Speckit feature branch: Run
.specify/scripts/bash/check-prerequisites.sh --json --paths-onlyfrom the repo root. If it succeeds and returns aFEATURE_DIRwith atasks.md, this is a Speckit strategic workflow. Read the full contents of.opencode/commands/speckit.implement.mdand delegate it to thecobalt-crush-devagent via the Task tool — pass the command file's instructions as the agent's prompt so the agent executes the implementation workflow. -
Check for an OpenSpec active change: Look for directories under
openspec/changes/that contain atasks.mdfile. If one exists, this is an OpenSpec tactical workflow. Validate branch: Rungit rev-parse --abbrev-ref HEAD. The current branch must beopsx/<change-name>where<change-name>matches the detected change directory name. If not on the correct branch, STOP with error:"OpenSpec change
<name>detected but you are on branch<current-branch>. Run:git checkout opsx/<name>"
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.
- 10d ago First seen · 112 lines · 45 tokens per session scan A c89a4681f045
uf.cobalt-crush is a command published in the GitHub repository unbound-force/gaze (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 45 tokens to every session and 999 once invoked, about $0.0002 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.