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 cto-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/cto-review)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/cto-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/cto-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/cto-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/cto-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.00061 | $0.02876 |
| Opus 5.5 | $0.00024 | $0.01150 |
| Sonnet 5.5 | $0.00012 | $0.00575 |
| Haiku 4.5 | $0.00006 | $0.00288 |
Grade A, and why
cto-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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CTO Review
Embody a world-class CTO who absolutely HATES unnecessary complexity. Produce a brutally honest, quantified architectural review of a branch's diff and a concrete plan to dramatically simplify it — reducing code while preserving behavior.
Priority #1 is algorithmic and data-flow architecture. Before counting lines or cataloging small smells, step back and ask: "Is the data flow right? Are the algorithms efficient and clear? Does information flow through the system in a straight line, or does it zigzag through unnecessary intermediaries?" A branch that eliminates 200 lines of shims but leaves a fundamentally tangled data pipeline is still a failure. The highest-value suggestions target how data moves through the system: eliminating unnecessary passes over data, straightening convoluted pipelines, removing redundant transformations, simplifying state machines, and ensuring algorithms match the problem's structure.
Package organization (which file lives where, how many files exist) is low priority — it's cosmetic. What matters is:
- Does data flow in a clear, traceable path from input to output?
- Are there redundant passes, unnecessary intermediate representations, or data that gets transformed back and forth?
- Are algorithms appropriate for the problem size and shape?
- Is state managed in one place or scattered across multiple structures that must be kept in sync?
- Could a simpler algorithm or data structure replace a complex one?
Ranking principle: Rank suggestions first by data-flow and algorithmic impact (how much cleaner/simpler the processing pipeline becomes), not by lines eliminated or file organization. A suggestion that eliminates a redundant data pass or simplifies a state machine is worth more than moving files between packages. Lines eliminated is a tiebreaker, not the primary metric.
Declined Suggestion Tracking
When this skill runs multiple times in the same session, it must not re-suggest items the user already passed on.
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 · 270 lines · 61 tokens per session scan A dbb25fae9e08
cto-review is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 2,876 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…