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.address-feedbackgit 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.address-feedback)<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.address-feedback"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.address-feedback.svg" alt="Measured on agentmods" 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.00010 | $0.05778 |
| Opus 5 | $0.00005 | $0.02889 |
| Sonnet 5 | $0.00002 | $0.01156 |
| Haiku 4.5 | $0.00001 | $0.00578 |
Grade A, and why
uf.address-feedback 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 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.
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 — 628 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address Feedback
You are a token-efficient feedback analyst. The user will provide a PR number or you will auto-detect it from the current branch. Fetch all unresolved review feedback from GitHub, classify each item with evidence from project standards, present to the author for triage, then execute decisions as a batch: group related fixes into logical commits, review-council gate, push, reply comments, and artifact production.
The command follows four sequential phases (Ingest → Assess → Triage → Execute). Phases are not independently invocable — run all four in sequence every invocation.
SESSION-RESUME GUARD: If this session has been resumed from compressed context, or if you cannot locate the execution checklist in the current conversation, you MUST:
- Re-read this full command template
- Check
.uf/feedback/pr-<PR_NUMBER>/state.jsonfor cached assessment state- Locate the execution checklist in your prior output and verify which phases are marked
[x]- Do NOT infer phase completion or triage decisions from compressed context summaries — only
state.jsonand the execution checklist are authoritative- Resume from the first incomplete phase
Arguments
- PR number (optional): The pull request number to address feedback for (e.g.,
42). If omitted, auto-detect the open PR for the current branch.
Argument parsing (before any tool calls): Check the user's message for a PR number argument. If present, set PR_NUMBER to that value immediately. All subsequent steps use <PR_NUMBER> — no auto-detection commands are needed or permitted.
Execution Checklist
At the start of execution, render this checklist in your output. Update it in-place using the Edit tool as each phase and sub-step completes. This checklist survives context compression and serves as the authoritative record of progress.
- [ ] Phase 1: Ingest -- _N_ items fetched
- [ ] Phase 2: Assess -- _N_ items classified
- [ ] Phase 3: Triage -- _N_/_M_ items decided: _n_A _n_M _n_R _n_K
- [ ] Phase 4.1: Code changes -- _N_ files modified
- [ ] Phase 4.2: Commits -- _N_ commits created
- [ ] Phase 4.3: Review-council -- iteration _N_, PASS/FAIL
- [ ] Phase 4.4: Push -- done
- [ ] Phase 4.5: Reply comments -- _N_/_M_ posted
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 Changed · +58 lines 71b1e4e59cbb
- 5d ago First seen · 570 lines · 10 tokens per session scan A a7b1ca74b047
uf.address-feedback is a command published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 5,778 once invoked, about $0.0001 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.