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 JoaoEquer/Oficina --skill design-auditgit clone --depth 1 https://github.com/JoaoEquer/OficinaWrote 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/joaoequer/oficina/design-audit)<a href="https://agentmods.dev/skills/joaoequer/oficina/design-audit"><img src="https://agentmods.dev/badge/skills/joaoequer/oficina/design-audit/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/joaoequer/oficina/design-audit"><img src="https://agentmods.dev/badge/skills/joaoequer/oficina/design-audit.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.00172 | $0.01546 |
| Opus 5.5 | $0.00069 | $0.00618 |
| Sonnet 5.5 | $0.00034 | $0.00309 |
| Haiku 4.5 | $0.00017 | $0.00155 |
Grade A, and why
design-audit 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design audit
Provenance: own skill (2026-10-19). Rule catalog adapted from Impeccable's detector (pbakaus/impeccable, Apache-2.0,
antipatterns.json); confidence model borrowed from getsentry/skillssecurity-review(Apache-2.0). Why:redesign-existing-projectsis a taste checklist with no detection step, and its "Upgrade Techniques" recommend several patterns that are themselves generated-UI tells (Geist, glassmorphism, spotlight borders, grain overlays). This skill wins when the two disagree.
Report only. Never edit files in this skill.
Core idea
A single purple gradient is not "AI slop". The tell is the default taken without a reason, repeated. A finding needs: a pattern from the catalog, evidence (file:line or a screenshot region), and no documented reason for it in the project (brand guide, DESIGN.md, tokens). Brand choices beat the catalog: if DESIGN.md says the brand font is Inter, Inter is not a finding.
Process
1. Context (5 min, before any scan)
- Stack: framework, styling (Tailwind v3/v4, CSS modules, styled, RN
StyleSheet), component kit (shadcn, MUI, NativeWind...). Check everypackage.json, not only the root. - Design system source of truth, in order:
DESIGN.md/ brand doc → token files (tailwind.config.*,@themein CSS,theme.ts, CSS custom properties) → none. No source = say so; drift findings then become "no system" findings. - Product character in one line (who uses it, what mood). A tax dashboard and a kids' game have different correct answers. Canvas/game art drawn in code is not token drift.
2. Static scan (deterministic)
node <oficina>/skills/design-audit/scripts/scan.mjs <project-path> --max 8
node <oficina>/skills/design-audit/scripts/scan.mjs <project-path> --json # for diffing two runs
Read-only, no network, no deps. Output groups: tell, drift, a11y, plus aggregates (distinct colors/radii/font sizes). Treat every hit as a lead: open the file:line and confirm before it becomes a finding. Monorepo: run per app.
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.
- 3d ago First seen · 81 lines · 172 tokens per session scan A 4d98470977e9
design-audit is a skill published in the GitHub repository JoaoEquer/Oficina (2 stars, last pushed 4d ago), licensed MIT. It adds 172 tokens to every session and 1,546 once invoked, about $0.0007 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-10-21.
Other skills, from other repositories
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
ui-mockup
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
frontend-design
Give a web page or app its own look instead of a generic AI-made one: choose colors, type and layout on purpose before building, then critique the result. Use when building a new interface or reshaping an existing one.
frontend-ui-ux-system
A company-level guide for designing web interfaces and user experiences. It covers visual styles, design tokens (named values for colors, spacing, and typography), layout, interaction, accessibility, motion, and review checks.
accessibility-audit
Check a live page against the barriers that actually lock people out — keyboard, contrast, labels, focus — each with the fix.