requesting-code-review

requesting-code-review is a skill for Claude Code, Codex from dork-labs/dorkos. It costs 39 tokens per session (1,673 once invoked), scanned A, original, MIT.

Guides dispatching a code-reviewer subagent to verify work before proceeding. Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

Skill for Claude CodeCodex

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 skills/dork-labs/dorkos/requesting-code-review
Any agent
npx skills add dork-labs/dorkos --skill requesting-code-review
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

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 requesting-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/dork-labs/dorkos/requesting-code-review.svg)](https://agentmods.dev/skills/dork-labs/dorkos/requesting-code-review)
Your own site
<a href="https://agentmods.dev/skills/dork-labs/dorkos/requesting-code-review"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/requesting-code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,673 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00039 $0.01673
Opus 5 $0.00019 $0.00837
Sonnet 5 $0.00008 $0.00335
Haiku 4.5 $0.00004 $0.00167

Measured today against content hash ef845c047af0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requesting-code-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 today.

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/skills/requesting-code-review/SKILL.md · 190 lines

How it starts

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

Requesting Code Review

Dispatch a code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Core principle: Review early, review often.

When to Request Review

Mandatory:

  • After each batch of related tasks in spec-driven development (/flow:execute) — holistic batch-level review, not per-task review
  • After completing a major feature
  • Before merge to main

Optional but valuable:

  • When stuck (fresh perspective)
  • Before refactoring (baseline check)
  • After fixing a complex bug

Lightweight Alternative

For quick self-review without dispatching a subagent, trace through recently modified functions yourself to verify correctness and completeness inline. Use the full code-reviewer subagent (below) for deeper, more rigorous review.

How to Request

1. Get git SHAs

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main for full branch review
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code-reviewer subagent

Use the Agent tool with subagent_type: "code-reviewer". Supply the following context:

Required context:

  • {WHAT_WAS_IMPLEMENTED} — What you just built
  • {PLAN_OR_REQUIREMENTS} — What it should do (spec path, task description, or requirements)
  • {BASE_SHA} — Starting commit
  • {HEAD_SHA} — Ending commit
  • {DESCRIPTION} — Brief summary of the changes

DorkOS-specific review concerns to include:

  • FSD layer violations (shared <- entities <- features <- widgets)
  • Transport interface compliance (HttpTransport / DirectTransport)
  • SDK import confinement — each runtime SDK stays in its adapter directory: @anthropic-ai/claude-agent-sdkservices/runtimes/claude-code/, @openai/codex-sdkservices/runtimes/codex/, @opencode-ai/sdkservices/runtimes/opencode/
  • os.homedir() ban (must use lib/dork-home.ts)
  • TSDoc on exports
  • Tailwind class sorting (prettier-plugin-tailwindcss)
  • Barrel import conventions (import from index.ts, never internal paths)

Read the full file on GitHub · 190 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. today First seen · 190 lines · 39 tokens per session scan A ef845c047af0

Subscribe to this mod's changes

requesting-code-review is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,673 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-09-03.