Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jangles-byte/ateliernpx agentmods add skills/jangles-byte/atelier/critiqueWrote 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/jangles-byte/atelier/critique)<a href="https://agentmods.dev/skills/jangles-byte/atelier/critique"><img src="https://agentmods.dev/badge/skills/jangles-byte/atelier/critique/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/jangles-byte/atelier/critique"><img src="https://agentmods.dev/badge/skills/jangles-byte/atelier/critique.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.00123 | $0.00663 |
| Opus 5.5 | $0.00049 | $0.00265 |
| Sonnet 5.5 | $0.00025 | $0.00133 |
| Haiku 4.5 | $0.00012 | $0.00066 |
Grade A, and why
critique 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique
A critique is an ordered list of changes with exact values, produced by evaluating a real render against a fixed rubric. "Feels unbalanced" is not critique; "increase section gap 32px→64px so the pricing table separates from the hero" is.
Workflow
- Get a real render. Screenshot the running artifact (browser preview, simulator,
plot output, game capture) — never critique source code or imagination.
If anything moves, a still is not a render. Capture the motion and watch it:
Then interact with it directly — hover, open and close, mash the trigger — because interruption bugs only appear under abuse.../motion/scripts/capture-motion.py index.html --out review.gif --duration 1200 - Inventory — one paragraph of what is objectively on screen (elements, reading order as encountered, palette, faces in use). Forces looking before judging.
- Score the rubric — eight dimensions, 1–5 each, using references/rubric.md. Cite evidence per score.
- Write the change list — every scored weakness becomes a change in the exact format of references/change-format.md: ranked by impact, each with location, current value → new value, and the principle it serves. 3 changes minimum, 10 maximum; past 10, ship the top 10 and re-critique after.
- Apply and re-render. A critique that isn't applied and re-verified is a memo. Iterate until the weakest rubric dimension scores ≥ 4 or the user stops you.
Which reference to load
| Situation | Load |
|---|---|
| Scoring any render; the eight dimensions with anchors | references/rubric.md |
| Writing the output; worked example of a full critique | references/change-format.md |
Rules
- Judge against the design philosophy first (does it keep its own promises?), the rubric second. If no philosophy exists, write a one-line inferred intent and say so.
- Diagnose over prescribe when uncertain of intent — but never emit a finding without a proposed exact value. Uncertainty goes in a parenthetical, not in vagueness.
- Strengths get one sentence, findings get the rest. Flattery is not calibration.
- Accessibility findings (contrast, motion, hit targets) always rank above aesthetic findings, whatever their scores.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 49 lines · 0 tokens per session scan A c2a7f108ac56
critique is a skill published in the GitHub repository jangles-byte/atelier (3 stars, last pushed 2mo ago), licensed MIT. It adds 123 tokens to every session and 663 once invoked, about $0.0005 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
Design Resources
This skill provides a curated design reference library for all Maxim design agents. It contains typography scales, color systems, component patterns, animation specs, accessibility checklists, critique frameworks, and the 9-section DESIGN.md standard template.
paint
Paint a complete visual universe with genjutsu - art direction brainstorm, design system, implementation, audit. Anti-AI-slop design pipeline. Adapts to Web, Android (Compose), Apple (SwiftUI).
compose-graphics
Advanced Compose visuals - Material 3 Expressive motion physics, AGSL shaders (Android 13+), Canvas/DrawScope generative, graphicsLayer effects.
swiftui-motion
SwiftUI animation foundations - withAnimation, transitions, matchedGeometryEffect, PhaseAnimator, KeyframeAnimator, springs, gestures.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
mobile-principles
Mobile-specific UX principles - touch targets, hover-less doctrine, thumb zones, safe areas, gestures, mobile perf budgets. Cross-platform (web mobile, iOS, Android).