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 agentmods add skills/context4ai/workflow/designnpx skills add context4ai/workflow --skill designgit clone --depth 1 https://github.com/context4ai/workflowWhat 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 | $0.00042 | $0.02826 |
| Opus 5 | $0.00021 | $0.01413 |
| Sonnet 5 | $0.00008 | $0.00565 |
| Haiku 4.5 | $0.00004 | $0.00283 |
Grade A, and why
design 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 yesterday.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design
A frontend page design system guide for the C4A project. This skill auto-loads when creating or modifying frontend pages, providing design tokens, component specs, page templates, layout references, and key design rules.
When This Skill Triggers
This skill should be loaded whenever the agent is:
- Creating a new frontend page or view
- Modifying the layout or visual structure of an existing page
- Adding or changing UI components on a page
- Working on styling, theming, or responsive behavior
- Reviewing frontend code for design system compliance
Design System File Hierarchy
Required Reads (Always Load)
These files MUST be read before any frontend page work:
| File | Path | Contents |
|---|---|---|
| DESIGN.md | ${CLAUDE_PLUGIN_ROOT}/design/ui/reference/DESIGN.md |
Full design system specification — colors, typography, elevation, layout, components, interaction rules, do's and don'ts |
| _tokens.css | ${CLAUDE_PLUGIN_ROOT}/design/ui/templates/_tokens.css |
CSS custom properties (all --c4a-* tokens) for dark and light themes |
On-Demand Reads (Load When Relevant)
| File | Path | When to Load |
|---|---|---|
| design-guide.md | ${CLAUDE_PLUGIN_ROOT}/design/ui/reference/design-guide.md |
When making template selection decisions or implementing detailed card/spacing/typography patterns |
| Component specs | ${CLAUDE_PLUGIN_ROOT}/design/ui/components/<name>.md |
When using a specific component type (see component list below) |
| Page templates | ${CLAUDE_PLUGIN_ROOT}/design/ui/templates/<template>.html |
When creating a page that matches a template pattern |
| _base.css | ${CLAUDE_PLUGIN_ROOT}/design/ui/templates/_base.css |
When implementing structural CSS classes |
Component Spec Files
| File | Components Covered |
|---|---|
buttons.md |
Primary, Secondary, Ghost buttons |
badges-status.md |
Badges, tags, status indicators |
cards.md |
Card structures, padding, spacing |
dialogs.md |
Modals, error dialogs, dialog shell |
dropdowns-menus.md |
Dropdown menus, select triggers |
empty-states.md |
Standard empty state, dashed placeholder |
forms.md |
Input, select, toggle, selection cards, labels |
navigation.md |
Sidebar, breadcrumbs, tabs |
tables.md |
Data tables, table containers |
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.
- yesterday First seen · 245 lines · 42 tokens per session scan A 4716ae0addeb
design is a skill published in the GitHub repository context4ai/workflow (4 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 2,826 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…