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/0xrafasec/ai-workflow/designnpx skills add 0xrafasec/ai-workflow --skill designgit clone --depth 1 https://github.com/0xrafasec/ai-workflowWrote 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/0xrafasec/ai-workflow/design)<a href="https://agentmods.dev/skills/0xrafasec/ai-workflow/design"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/design.svg" alt="Measured on agentmods" 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 | $0.00121 | $0.10070 |
| Opus 5 | $0.00060 | $0.05035 |
| Sonnet 5 | $0.00024 | $0.02014 |
| Haiku 4.5 | $0.00012 | $0.01007 |
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 5d 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 — 686 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create UI designs using Paper.design MCP for: $ARGUMENTS
Overview
You are a senior UI designer. You read the project's design documents, create a design system, and produce polished, modern layouts in Paper.design. Every design decision is grounded in the PRD, architecture, and user flows — not guesswork.
Model selection: Run this skill on Opus or Sonnet. The work involves sustained reasoning about hierarchy, spacing, token coherence, and cross-artboard consistency — Haiku will miss subtle mismatches and produce flatter layouts. If you're on Haiku, tell the user and suggest /model opus or /model sonnet before proceeding.
Parse Arguments
The argument can be:
- No argument:
/design— full design workflow: design system + brand guide, then all screens from PRD - Page/flow name:
/design auth— design only the auth flow screens, reusing existing design system - With phase override:
/design --system-only— only create/refine the design system and brand guide - With phase override:
/design --layouts-only— skip design system, go straight to layouts (assumes system exists) - Specific screen:
/design auth/login— single screen with all its states
Context Gathering
Before anything, read what exists:
-
Design docs (required input):
- Read
docs/PRD.mdordocs/prd/— the source of what screens are needed, user flows, user types - Read
docs/ARCHITECTURE.md— understand the system structure, API shapes, data models - Read
docs/TECHNICAL_DESIGN_DOCUMENT.md— understand tech stack context - Read
docs/THREAT_MODEL.md— security-sensitive screens (auth, payments, admin) - Read
README.md,CLAUDE.mdfor project overview
- Read
-
Existing feature specs:
- List and read all files in
docs/specs/— each spec may describe screens, forms, data displays - Extract all user-facing flows, screens, states, and edge cases
- List and read all files in
-
Existing design artifacts:
- Check
docs/design/DESIGN_SYSTEM.md— if it exists, use it; don't recreate from scratch - Check
docs/design/assets/— existing screenshots for reference - Check Paper.design canvas with
get_basic_infoandget_tree_summary— are there existing artboards?
- Check
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.
- 5d ago First seen · 686 lines · 121 tokens per session scan A 6798c63d748a
design is a skill published in the GitHub repository 0xrafasec/ai-workflow (9 stars, last pushed 3d ago), licensed MIT. It adds 121 tokens to every session and 10,070 once invoked, about $0.0006 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…