gza-task-review

gza-task-review is a skill for Claude Code, Codex from mhawthorne/gza. It costs 31 tokens per session (4,341 once invoked), scanned A, original, MIT.

An interactive code review for a Gza task's implementation branch. It examines the code, changes, and task scope, then produces structured findings for gza-task-improve.

In plain words
What is it for?
Reviewing a task's implementation and optionally posting the findings as a pull-request comment. It requires the full task ID, such as gza-1234.
Why use it?
It provides human-guided review after automated review attempts are exhausted, without mixing in separate verification work.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Good fit Reviewing a task's implementation and optionally posting the findings as a pull-request comment. It requires the full task ID, such as gza-1234.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mhawthorne/gza/gza-task-review
Install

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.

Any agent
npx skills add mhawthorne/gza --skill gza-task-review
Clone the repo
git clone --depth 1 https://github.com/mhawthorne/gza

Made for: Claude Code, Codex.

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 gza-task-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mhawthorne/gza/gza-task-review"><img src="https://agentmods.dev/badge/skills/mhawthorne/gza/gza-task-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,341 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 238
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Agent Snooping · line 317
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00031 $0.04341
Opus 5 $0.00015 $0.02171
Sonnet 5 $0.00006 $0.00868
Haiku 4.5 $0.00003 $0.00434

Measured 3d ago against content hash 45aa949ecbc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

gza-task-review 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 3d 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.

src/gza/skills/gza-task-review/SKILL.md · 319 lines

How it starts

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

Gza Task Review

Run an interactive code-only review for a specific gza task. Review the current code, diff, and scope only; verification is handled elsewhere in the lifecycle. Produces structured review output that /gza-task-improve can consume. Use this when automated review iterations are exhausted, or when you want to review a task interactively.

Inputs

  • Required: full prefixed task ID (for example, gza-1234)
  • Optional: --pr — also post the review as a PR comment

If the user did not provide a task ID, ask for it before proceeding.

Use the full prefixed task ID as provided.

Process

Step 0: Confirm review inputs without switching branches

Manual /gza-task-review must stay compatible with repositories that forbid ad hoc git commands. Do not run git checkout, git switch, or other manual branch-switching commands as part of this skill.

Before proceeding, make sure at least one of these is true:

  • The current workspace/worktree was already prepared on the implementation checkout by Gza or another documented non-forbidden workflow, so running verify_command here will evaluate the intended implementation.
  • The caller already provided authoritative diff context, so the review can use that diff even if this workspace is not on the implementation checkout.

If neither is true, stop and ask the user to either:

  • rerun /gza-task-review from a prepared implementation checkout/worktree, or
  • provide the authoritative implementation diff explicitly.

Step 1: Resolve the task

Query the task database to get task details and branch:

uv run python -c "
import json, sys
from pathlib import Path
from gza.config import Config
from gza.db import SqliteTaskStore

config = Config.load(Path.cwd())
store = SqliteTaskStore.from_config(config)
task = store.get(<TASK_ID>)
if not task:
    print('ERROR: Task not found', file=sys.stderr)
    sys.exit(1)

# If given a review or improve task, resolve to the implementation task
impl_task = task
if task.task_type == 'review' and task.depends_on:
    impl_task = store.get(task.depends_on)
elif task.task_type == 'improve' and task.based_on:
    impl_task = store.get(task.based_on)

# Check for existing reviews
assert impl_task.id is not None
reviews = store.get_reviews_for_task(impl_task.id)
latest_review = reviews[0] if reviews else None

print(json.dumps({
    'impl_task_id': impl_task.id,
    'impl_task_type': impl_task.task_type,
    'impl_branch': impl_task.branch,
    'impl_prompt': impl_task.prompt,
    'impl_status': impl_task.status,
    'impl_tags': list(impl_task.tags),
    'has_existing_review': latest_review is not None,
    'existing_review_id': latest_review.id if latest_review else None,
    'verify_command': config.verify_command,
}, default=str))
"

Read the full file on GitHub · 319 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. 3d ago Changed · +1 lines 45aa949ecbc3
  2. 8d ago Changed · +7 lines d560f7a9ac2c
  3. 12d ago First seen · 311 lines · 31 tokens per session scan A ee0ca93eae47

Subscribe to this mod's changes

gza-task-review is a skill published in the GitHub repository mhawthorne/gza (12 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 4,341 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-30.