gaze: Skill for OpenCode

.opencode/skills/review-context/SKILL.md

review-context is a skill for OpenCode from unbound-force/gaze. It costs 21 tokens per session (1,916 once invoked), scanned A, original, Apache-2.0.

A shared review tool that finds the documents and context connected to a change before review begins. It can load specifications, linked issues, path classifications, and a walkthrough summary in a fixed order.

In plain words
What is it for?
Use it before pull-request or local reviews to locate the governing specification, related issues, and affected parts of the project.
Why use it?
It reduces the chance that a review misses the original requirements or important surrounding context.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is unbound-force/gaze's own configuration. It tells OpenCode how to work on gaze itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gaze configures →

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/skills/review-context/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/unbound-force/gaze

Made for: 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.

agentmods badge for review-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/unbound-force/gaze/review-context/github.svg)](https://agentmods.dev/skills/unbound-force/gaze/review-context)
Your own site
<a href="https://agentmods.dev/skills/unbound-force/gaze/review-context"><img src="https://agentmods.dev/badge/skills/unbound-force/gaze/review-context/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.

agentmods 80×15 button for review-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/unbound-force/gaze/review-context"><img src="https://agentmods.dev/badge/skills/unbound-force/gaze/review-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,916 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01916
Opus 5.5 $0.00008 $0.00766
Sonnet 5.5 $0.00004 $0.00383
Haiku 4.5 $0.00002 $0.00192

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

Security

Grade A, and why

review-context 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/skills/review-context/SKILL.md · 258 lines

How it starts

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

Skill: Review Context Discovery

Shared logic for discovering and loading review context before a review command begins its analysis. Consuming commands load this skill to standardize how spec artifacts, linked issues, path classifications, and walkthrough summaries are discovered and formatted.

Consumers

Command How it loads Notes
/uf.review-pr Skill tool Replaces inline Steps 6-8 logic
/uf.review-council Skill tool Phase 1c — Protocols 1, 3, 4; Protocol 2 conditional (explicit PR number only)
/uf.address-feedback Skill tool Replaces inline fallback (line 143)

The consuming command specifies which protocols to execute based on the available inputs (e.g., a local review has no PR body to parse for issue links).


Protocol 1: Spec Artifact Discovery

Locate the specification associated with the current change. The discovery order is deterministic — stop at the first match.

Step 1: Branch name matching

Derive the spec directory from the current branch name or PR branch name:

Branch pattern Spec location
speckit/NNN-<name> or NNN-<name> (legacy) specs/<name>/spec.md (Speckit; strip speckit/ prefix)
opsx/<name> openspec/changes/<name>/proposal.md (OpenSpec changes)
opsx/<name> openspec/specs/<name>/spec.md (OpenSpec specs)

Step 2: PR description parsing

If no spec is found via branch name and a PR description is available, scan for explicit spec references (e.g., "See spec 012" or "Implements specs/012-swarm/spec.md" or "branch speckit/012-swarm").

Step 3: Changed-file detection

If no spec is found via branch name or PR description, check the changed file list for spec artifacts. The spec may be introduced by the change itself. If found in changed files, read the spec content from the diff rather than from the filesystem.

Step 4: Read relevant sections

When a spec is found, read only the sections relevant to review to minimize token usage:

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

  1. 8d ago Changed b37604d4bcbc
  2. 1mo ago Changed 90619822293f
  3. 2mo ago First seen · 258 lines · 21 tokens per session scan A 1ea567fe0d3c

Subscribe to this mod's changes

review-context is a skill published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,916 once invoked, about $0.0001 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-09-03.

Related

review-context compared with skills from other repositories

review-context next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
review-contextunbound-force/gazeSkill4yesterdayApache-2.0A21OpenCode
autoreviewopenclaw/clawhubSkill9.5kyesterdayMITA17Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skillsSkill2.2k5d agoMITA115Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermesSkill5.2ktodayMITA48Claude Code, Codex
revdiff-planumputun/revdiffSkill945yesterdayMITA84Claude Code
explore-unknownsdzhng/skillsSkill1.4k2d agoMITA162Claude Code, Codex
re0-mergeLilMGenius/paperthinSkill1.4k4d agoMITA70Claude Code