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-initgit 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-init)<a href="https://agentmods.dev/skills/aysnc-labs/angora/angora-design-system-init"><img src="https://agentmods.dev/badge/skills/aysnc-labs/angora/angora-design-system-init/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-init"><img src="https://agentmods.dev/badge/skills/aysnc-labs/angora/angora-design-system-init.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.00173 | $0.05489 |
| Opus 5 | $0.00086 | $0.02745 |
| Sonnet 5 | $0.00035 | $0.01098 |
| Haiku 4.5 | $0.00017 | $0.00549 |
Grade A, and why
angora-design-system-init 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 10d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Everything in this repo is scaffolding. Existing components, design system pages, wireframes, tokens, and system.md are all starter placeholders — not approved design work. Use their file structure but replace all content. Nothing here is precious.
Resumability
Before starting, check system.md for an Init Progress section at the bottom. If it exists:
- Read the completed steps — skip them entirely.
- Resume from the first uncompleted step.
- If a step has pending user decisions noted (e.g., "needs: icon set from user"), ask for those before building.
- Tell the user where you're resuming from: "Picking up from Step X — [step name]. Last completed: [previous step]."
If no Init Progress section exists, this is a fresh start — begin at Phase 1.
Progress tracking: After completing each step, update the Init Progress section in system.md immediately. Mark the step as done, note any pending decisions for the next step. This ensures the process survives context compression and new sessions.
Phase 1 resumability: Since Phase 1 is a multi-step conversation, record each answer in Init Progress as it's received (e.g., "Step 2 done — audience: mid-stage startup CTO evaluating developer tools"). Include reference analysis notes if applicable. This way a new session can pick up mid-conversation without re-asking questions the user already answered.
Roadmap
At the start of the process (or when resuming), present the full build sequence to the user so they always know what's ahead:
Here's what we're building (you'll approve at each checkpoint):
- Creative direction — audience, feel, color world, signature element, anti-patterns, dark mode decision
- Tokens + style guide — OKLCH palette, semantic tokens, type, spacing, shadows, radii in browser
- Dark mode (if opted in) —
.darkoverrides, sidebar toggle, light/dark view routes- Buttons — sizes, variants, icon buttons
- Icons — starter icon set as components + downloadable SVGs
- Grid + Section — Section container component, section spacing rhythm, grid-gap utility, column patterns
- Cards — card types for your pages
- Forms — inputs, selects, checkboxes, radios, toggles, all states
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.
- 10d ago First seen · 234 lines · 173 tokens per session scan A 5d93dd6b0394
angora-design-system-init is a skill published in the GitHub repository Aysnc-Labs/angora (6 stars, last pushed 4mo ago), licensed MIT. It adds 173 tokens to every session and 5,489 once invoked, about $0.0009 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
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…
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…
motion-and-storytelling
Disney's 12 animation principles, cinematic storytelling techniques, and comic book conventions apply to web UI — used subtly, they make interfaces feel alive, intentional, and emotionally resonant. Use when designing transitions, micro-interactions, onboarding flows, scroll animations, or any motion in the UI.
responsive-paradigms
Mobile, tablet, and desktop are different interaction paradigms — not the same layout scaled up or down. Sections can be hidden, repositioned, or made sticky on mobile. Navigation and primary actions move. Use when designing responsive layouts, adapting desktop UI for mobile, or deciding what to show on each…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.