review-task

A read-only reviewer for individual software tasks. It checks whether a task is appropriately sized, clearly stated, testable, consistent, and linked to its source requirements.

In plain words
What is it for?
Use it to audit a task in backlog/tasks/ and receive an APPROVE or REVISE verdict.
Why use it?
It exposes vague goals, missing acceptance checks, oversized work, and broken links to the broader plan before implementation begins.

Command for Claude Code

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.

agentmods
npx agentmods add commands/iolairus/borderlint/review-task
Clone the repo
git clone --depth 1 https://github.com/iolairus/borderlint

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 85 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00085
Opus 5 $0.00004 $0.00043
Sonnet 5 $0.00002 $0.00017
Haiku 4.5 $0.00001 $0.00009

Measured 2d ago against content hash 82be83c629ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/commands/review-task.md · 9 lines

What it actually says

Delegate this work to the task-reviewer subagent (read-only reviewer) and relay its full report to the user.

Review the task $ARGUMENTS under backlog/tasks/. Apply the full checklist (sizing, goal quality, acceptance criteria, consistency, traceability). Give a verdict: APPROVE or REVISE.

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. 2d ago First seen · 9 lines · 8 tokens per session scan A 82be83c629ee

Subscribe to this mod's changes

review-task is a command published in the GitHub repository iolairus/borderlint (7 stars, last pushed 10d ago), licensed MIT. It adds 8 tokens to every session and 85 once invoked, about $0.0000 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.