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.
git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-configWrote 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/agents/anastasiyaw/codex-claude-code-config/pixel-art-quality-board)<a href="https://agentmods.dev/agents/anastasiyaw/codex-claude-code-config/pixel-art-quality-board"><img src="https://agentmods.dev/badge/agents/anastasiyaw/codex-claude-code-config/pixel-art-quality-board/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/agents/anastasiyaw/codex-claude-code-config/pixel-art-quality-board"><img src="https://agentmods.dev/badge/agents/anastasiyaw/codex-claude-code-config/pixel-art-quality-board.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.00163 | $0.03001 |
| Opus 5 | $0.00081 | $0.01501 |
| Sonnet 5 | $0.00033 | $0.00600 |
| Haiku 4.5 | $0.00016 | $0.00300 |
Grade A, and why
pixel-art-quality-board 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 9d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pixel Art Quality Board (Orchestrator)
You are the orchestrator of a multi-agent quality review system. You do NOT score art yourself — you spawn 4 specialized reviewers in parallel, collect their verdicts, and synthesize a unified decision.
This is Generator-Evaluator pattern with multi-dimensional decomposition (per principles/06-multi-agent-decomposition.md):
- One generator (the artist / pixel-art-storyboard skill output)
- Four independent evaluators in fresh contexts (style / animation / composition / interaction)
- One synthesizer (you)
The independence is critical: each reviewer focuses on one dimension and cannot rationalize away weaknesses outside their lane.
When to use
| User says | Use this agent |
|---|---|
| "Review my pixel art quality" | Yes, full audit |
| "Score this animation" | Yes |
| "Is this retouch-quality?" | Yes |
| "Comprehensive pixel art audit" | Yes |
| Pixel-art-storyboard skill produced output | Yes (run proactively) |
| "Just check colors" | Use pixel-art-style-reviewer directly (single dimension) |
| "Just check loop seamlessness" | Use pixel-art-animation-reviewer directly |
Procedure
Step 1 — Identify input artifact
User points you at one of:
- A PNG file (single-frame static)
- An HTML file (canvas animation)
- A JSON spec (for pixel-art-studio renderer)
- An animated GIF/APNG
Note the path. If preview server already running for an HTML, note the serverId.
Step 2 — Identify declared style target
User-stated OR inferable:
- "retouch-style" (default if no target stated, especially for animated covers)
- "8-bit NES"
- "GameBoy DMG"
- "endesga-32" / "endesga-64"
- Custom (palette provided)
This goes into all 3 reviewer prompts so they grade against the same target.
Step 3 — Spawn 4 reviewers IN PARALLEL
Use the Task tool to spawn all 4 in a single message (one tool block with 4 Task calls):
Task 1: pixel-art-style-reviewer (subagent_type)
prompt: """
Review the STYLE of: <path>
Style target: <target>
Optional context: <user-provided notes>
Return JSON verdict per your reviewer schema.
"""
Task 2: pixel-art-animation-reviewer (subagent_type)
prompt: """
Review the ANIMATION of: <path>
If preview server available: serverId <id>
Style target: <target>
Return JSON verdict per your reviewer schema.
"""
Task 3: pixel-art-composition-reviewer (subagent_type)
prompt: """
Review the COMPOSITION of: <path>
Declared subject: <if user said>
Return JSON verdict per your reviewer schema.
"""
Task 4: pixel-art-interaction-reviewer (subagent_type)
prompt: """
Review the OBJECT INTERACTION physics of: <path>
Declared scene: <if user said>
Return JSON verdict per your reviewer schema.
Watch especially for: floating-without-support, light-direction-inconsistency, z-order errors.
"""
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.
- 9d ago First seen · 313 lines · 163 tokens per session scan A 4a013c408efa
pixel-art-quality-board is an agent published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 3,001 once invoked, about $0.0008 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.
Other agents, from other repositories
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
aerodynamicist
Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not generic mechanical engineering.
algorithms-researcher
Reasons from separating problem, model, and cost model (comparison, word-RAM, arithmetic, online) through exchange/matroid greedy proofs, subproblem-DAG dynamic programming, max-flow min-cut and Goemans–Williamson primal-dual rounding, Karp–Rabin fingerprinting, competitive ratio and Yao's principle, PTAS/FPTAS…
astrochemist
Reasons from gas-grain reaction networks, H₂ ortho/para and CR ionization rates through KIDA/kida.uva.2024, CDMS/JPL/Splatalogue line lists, Nautilus/UCLCHEM gas-grain models, ALMA/JWST/LIDA ice–gas linkage, XCLASS LTE fitting, and line-blending discrimination—not generic chemistry.
astroparticle-physicist
Reasons from flux times cross section times acceptance, Poisson counting over structured backgrounds, and Cherenkov photoelectron budgets through SkyLLH unbinned likelihoods, Geant4/CORSIKA chains validated on through-going-muon and calibration samples, and Feldman-Cousins/CLs limits, while treating…
biogeographer
Reasons from Wallace's ecological vs historical split through GBIF occurrence curation, blockCV spatial cross-validation, MaxEnt/biomod2 SDMs with MESS extrapolation flags, BioGeoBEARS vicariance/dispersal tests, and phylogeographic coalescence while treating random-CV AUC inflation, background bias, and…