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 Aysnc-Labs/angora --skill angora-design-system-auditgit clone --depth 1 https://github.com/Aysnc-Labs/angoraWrote 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/aysnc-labs/angora/angora-design-system-audit)<a href="https://agentmods.dev/skills/aysnc-labs/angora/angora-design-system-audit"><img src="https://agentmods.dev/badge/skills/aysnc-labs/angora/angora-design-system-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/aysnc-labs/angora/angora-design-system-audit"><img src="https://agentmods.dev/badge/skills/aysnc-labs/angora/angora-design-system-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.00160 | $0.03764 |
| Opus 5 | $0.00080 | $0.01882 |
| Sonnet 5 | $0.00032 | $0.00753 |
| Haiku 4.5 | $0.00016 | $0.00376 |
Grade A, and why
angora-design-system-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 11d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit: $ARGUMENTS
Before you start
- Read
src/system.md— intent, accessibility standard, anti-patterns, decisions log. - Read
src/styles/global.css— the token definitions you're validating against. - Read design-principles.md — the full set of design principles informing this review.
- Read tailwind-conventions.md — Tailwind v4 syntax rules to validate against.
- Determine the audit scope — is the target a component (
src/components/), a design system page (src/pages/design-system/), a layout (src/pages/design-system/layouts/), or a site page (src/pages/*.astro)? Some rules only apply to specific scopes (marked below). Layouts are full-page compositions — audit them like site pages (Page Rules apply) but note they use placeholder content, so skip SEO checks.
Then validate the target against the rules below.
Hard Rules (always enforced)
Tokens & Scoping
| Rule | Check |
|---|---|
| Token compliance | No arbitrary values. All styling via Tailwind utility classes referencing theme tokens |
| Semantic token enforcement | No raw palette utility classes. Components and pages must use only semantic token classes (bg-background, bg-card, text-foreground, text-muted-foreground, border-border, bg-primary, etc.). Grep for violations: bg-gray-*, text-gray-*, border-gray-*, bg-white, text-white, bg-black, text-black, bg-primary-[0-9], text-primary-[0-9], border-primary-[0-9] (raw scale references). The primitive palette lives outside @theme so these classes shouldn't exist — but inline styles, arbitrary values (bg-[#...], text-[var(--gray-*)]), and accidental palette references still need catching. Exception: style guide page (index.astro) uses inline style attributes with var(--gray-50) etc. for palette swatches — this is intentional |
| Pixel translation | No hard-coded pixel values in components. User-provided pixel values should map to the nearest theme token (e.g., "32px" → spacing-8 / p-8). If no token fits, use rem for sizing and em for prose-relative spacing. Flag any arbitrary [Xpx] values |
| Scoping | Component styles via Tailwind classes on elements. No global CSS selectors in component files |
| No true black | Never #000, rgb(0,0,0), or black. Use semantic tokens (text-foreground, bg-foreground) which resolve to near-black |
| No generated colors | No color-mix(), lighten(), darken(), or rgba() for text on colored backgrounds. All colors from semantic tokens or explicit palette values |
What ships with it
1 file 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.
- 11d ago First seen · 157 lines · 160 tokens per session scan A e978187c97b5
angora-design-system-audit is a skill published in the GitHub repository Aysnc-Labs/angora (6 stars, last pushed 4mo ago), licensed MIT. It adds 160 tokens to every session and 3,764 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-31.
Other skills, from other repositories
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
component-family-consistency
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…
modular-scale-typography
Typography feels cohesive and intentional when font sizes follow a modular scale — a ratio-based sequence where every size is mathematically related to the others. Use when defining type scales, setting up design tokens, reviewing font size choices, or when typography feels inconsistent or arbitrary.
extract-design
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…
algorithmic-color-palette
Derive a full UI colour palette algorithmically from one or two brand colours. Darker and lighter variants for interactive states, desaturated greys from the brand hue for borders and backgrounds, and semantic colours that feel coherent with the brand rather than generic. Use when building a colour system from scratch…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…