Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/unbound-force/gaze/uf.initgit clone --depth 1 https://github.com/unbound-force/gazeWhat 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 | $0.00044 | $0.08038 |
| Opus 5 | $0.00022 | $0.04019 |
| Sonnet 5 | $0.00009 | $0.01608 |
| Haiku 4.5 | $0.00004 | $0.00804 |
Grade B, and why
uf.init scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
or on Fedora/RHEL: `sudo dnf upgrade unbound-force` How it starts
The opening of the file, as written. The whole thing — 936 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: /uf.init
Description
Apply project-specific customizations to third-party tool files
that cannot be modified by the uf init Go binary. This command
uses LLM reasoning to read target files, understand their
structure, and intelligently insert customizations at the correct
locations.
When to run: After uf init (terminal), after uf setup,
or after updating the OpenSpec CLI (npm update). Safe to re-run
-- idempotent.
Instructions
Step 0: Command Directory Migration
Check whether the legacy .opencode/command/ directory needs
to be migrated to .opencode/commands/:
-
Check if
.opencode/command/exists (old directory):ls -d .opencode/command/ 2>/dev/null -
Check if
.opencode/commands/exists (new directory):ls -d .opencode/commands/ 2>/dev/null -
If old exists and new does NOT exist: rename the directory:
mv .opencode/command .opencode/commandsReport:
✅ command/ → commands/: migrated -
If both exist: move unique files from old to new, remove duplicates from old, and clean up:
# For each file in old dir, move if not in new, else remove for f in .opencode/command/*; do name="$(basename "$f")" if [ -f ".opencode/commands/$name" ]; then rm "$f" else mv "$f" .opencode/commands/ fi done rmdir .opencode/command 2>/dev/nullReport:
✅ command/ → commands/: merged (old dir cleaned up) -
If old does NOT exist: no migration needed. Report:
⊘ command/ migration: not needed
Step 1: Check Prerequisites
Verify the project has been initialized:
-
Check that
.opencode/directory exists. If not, STOP with:.opencode/not found. Runuf initfrom your terminal first. -
Check that these 4 OpenSpec skill files exist:
.opencode/skills/openspec-propose/SKILL.md.opencode/skills/openspec-apply-change/SKILL.md.opencode/skills/openspec-archive-change/SKILL.md.opencode/skills/openspec-explore/SKILL.md
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 First seen · 936 lines · 44 tokens per session scan B 07d6dc65b82c
uf.init is a command published in the GitHub repository unbound-force/gaze (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 44 tokens to every session and 8,038 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.