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/magicpatterns/agent-plugins/integrate-magic-patterns-designnpx skills add magicpatterns/agent-plugins --skill integrate-magic-patterns-designgit clone --depth 1 https://github.com/magicpatterns/agent-pluginsWhat 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.00087 | $0.01876 |
| Opus 5 | $0.00044 | $0.00938 |
| Sonnet 5 | $0.00017 | $0.00375 |
| Haiku 4.5 | $0.00009 | $0.00188 |
Grade A, and why
integrate-magic-patterns-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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate a Magic Patterns Design
Magic Patterns generates prototypes. The code you receive is a high-fidelity design spec — it shows layout, hierarchy, spacing rhythm, interactions, and intent. It is NOT meant to be pasted into a codebase as-is.
The golden rule: when the Magic Patterns code and the target codebase disagree, the codebase wins. Reproduce the design, not the exact code. Always prefer the codebase's existing components, design tokens, styling system, data layer, and conventions over the literal values in the prototype.
What Magic Patterns code looks like
Unless the design used a custom design system, expect:
- React 18 + TypeScript, styled with Tailwind CSS v3 utility classes
- lucide-react icons, framer-motion animations, react-router-dom routing, recharts charts
- Named exports (
export function PricingSection), flat or shallow file structure (components/,pages/,utils/) - Hardcoded mock data — inline arrays/objects or a
utils/mockData.ts - Placeholder images as full URLs (often Unsplash)
- Stubbed interactivity: controlled inputs with local
useState,onSubmithandlers that do nothing real, no API calls, no auth, no backend - Zip/GitHub exports are wrapped in a standalone Vite project (
vite.config.ts,index.html,src/)
Designs built on a design system preset (shadcn/ui, Chakra, Mantine, MUI) or a custom imported design system will use that library's components and theming instead of plain Tailwind.
Workflow
Step 1: Inventory the prototype
Read all the Magic Patterns files first. Identify:
- The actual design content: components, layout, screens, interactions, states (hover, empty, loading, error if present)
- Mock data shapes — these hint at the real data model the UI expects
- Which parts are scaffolding to discard (see checklist below)
Discard checklist — never port these:
-
index.tsx/index.html/vite.config.ts/tsconfig*.json/postcss.config.js/package.json/.eslintrc*— Vite scaffolding; your project already has its own -
tailwind.config.jsandindex.css— merge any genuinely new tokens into your existing config instead of replacing it -
canvas.manifest.js,useScreenInit.js— Magic Patterns multi-screen plumbing; replace with your real router -
ComponentPreview.tsx,components.config.json,context.md— editor preview files -
_designSystem/folders and empty component stub files — precompiled design system bundles -
data-idprops on elements — editor instrumentation -
utils/mockData.tsand inline mock data — replace with your real data layer
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 · 101 lines · 87 tokens per session scan A e4dfaa832aae
integrate-magic-patterns-design is a skill published in the GitHub repository magicpatterns/agent-plugins (0 stars, last pushed 27d ago), licensed MIT. It adds 87 tokens to every session and 1,876 once invoked, about $0.0004 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…