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 skills add hamzaPixl/pixl-ai --skill cross-reviewgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/skills/hamzapixl/pixl-ai/cross-review)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/cross-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/cross-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.
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/cross-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/cross-review.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01293 |
| Opus 5.5 | $0.00022 | $0.00517 |
| Sonnet 5.5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
cross-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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Independent review by two different Claude model tiers on the same diff. Produces a consensus table highlighting agreements, disagreements, and "taste decisions" where models diverge on subjective issues. Uses Sonnet (primary) + Haiku (secondary) by default — different model tiers catch different things due to reasoning depth differences.
How this differs from other review skills:
/code-review— single-model, multi-reviewer (same model, different lenses). This skill uses different models for independent validation./cto-review— architectural critique. This skill is diff-level review with cross-model consensus.
Cost note: This skill runs two full review passes. Reserve for critical changes (auth, payments, data integrity, public API contracts), not routine PRs.
Step 1: Get the Diff
Same as /code-review Step 1:
- PR number:
gh pr diff <number>,gh pr view <number> --json title,body,baseRefName - Branch name:
git diff main...<branch> - No argument:
git diff main...HEAD
Capture: full diff, list of changed files, PR description (if available).
Step 2: Parallel Independent Review
Spawn 2 agents in parallel, each with a different model. Both receive the identical diff and file list.
Agent A: Primary Model (Claude — Sonnet)
Agent(
subagent_type="Explore",
model="sonnet",
prompt="Review this code diff independently. For each finding, report: file, line, severity (Critical/Important/Minor), category (correctness/security/performance/convention), description, and confidence (1-100). Be thorough but only report findings you're confident about (>70%). Do not speculate.
Diff:
<full diff>
Changed files: <file list>
PR context: <description>
Return findings as a JSON array."
)
Agent B: Secondary Model (Haiku — fast, different perspective)
Agent(
subagent_type="Explore",
model="haiku",
prompt="<same prompt as Agent A with identical diff>"
)
Both agents run independently with no knowledge of each other's findings.
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.
- 1mo ago First seen · 130 lines · 55 tokens per session scan A 1079c7712ec4
cross-review is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 1,293 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…