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 cenconq25/claude-code-app-studio --skill quick-designgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/quick-design)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/quick-design"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/quick-design/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/cenconq25/claude-code-app-studio/quick-design"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/quick-design.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.00068 | $0.01647 |
| Opus 5 | $0.00034 | $0.00823 |
| Sonnet 5 | $0.00014 | $0.00329 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
quick-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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Design — Light Spec
For changes where opening /design-system would be heavyweight: copy tweaks, single-control re-designs, paywall-position changes, debounce tuning, error-message rewrites. The spec ends up embedded inside a story file, not as a standalone PRD.
Purpose / When to Run
Run when:
- A change is too small to update a full PRD section
- The PRD for the affected system is already complete and the change is a delta
- A bug fix has product implications worth recording
- The user types
/quick-designfor a one-off tweak
Do not run when:
- The change crosses multiple systems → use
/design-system - The change introduces a new system → use
/design-system - The change has no PRD context at all → use
/design-systemfrom scratch
Inputs
- Change name (required)
- Optional
--story <path>to embed the spec into a specific story - Existing PRD for the affected system if any
design/concept.md
Outputs
Either:
- A standalone
design/quick/<change-name>.md, OR - An appended
## Quick Design Specblock inside the named story file
Phase 1: Argument Resolution
If no change name is provided, ask:
- Prompt: "What is the change?"
- Free text — capture as kebab-case for filename.
Detect parent PRD: ask the user which existing PRD this change touches. Use Glob design/prd/*.md and offer the list as AskUserQuestion options if they don't know.
Detect mode:
--story <path>provided → embed mode- No flag → standalone mode (writes
design/quick/<change-name>.md)
Phase 2: Lightweight Context
Read only what is needed:
- The parent PRD section the change affects (not the whole PRD)
- The story file if embed mode
- Relevant entries in
design/design-bible.mdif the change is visual
Print a one-line context summary: "Change touches PRD <system>, section <name>. Embedding into story <NNN>."
Phase 3: Capture the Spec
Use a compact Q&A loop. Each question maps to a section of the spec.
- What is changing? (one sentence)
- Why? — link to a bug, metric goal, user feedback, or concept-doc principle
- Specifically what is the new behavior? — exact copy / value / sequence / position
- What is replaced? — exact prior behavior, so the diff is unambiguous
- Who does this affect? — all users / new users only / paying users / specific cohort
- Are there edge cases? — minimum required: offline, accessibility, dark mode if visual
- How will we know it worked? — one or two acceptance criteria in GIVEN-WHEN-THEN
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 · 184 lines · 68 tokens per session scan A f61a348c9686
quick-design is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,647 once invoked, about $0.0003 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-09-03.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…