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/upload-to-magic-patternsnpx skills add magicpatterns/agent-plugins --skill upload-to-magic-patternsgit 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.00071 | $0.01349 |
| Opus 5 | $0.00036 | $0.00674 |
| Sonnet 5 | $0.00014 | $0.00270 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade C, and why
upload-to-magic-patterns scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Then delete the temp working directory (`rm -rf "$TMP"`) so nothing is left in the user's project. How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upload local UI to Magic Patterns
Use this skill to push UI from the current codebase into a hosted Magic Patterns design and hand back the editor link. You port the local UI into a Magic Patterns-ready React file set with the recreate-as-react skill, then write those files into a blank design directly — you do not prompt Magic Patterns to generate anything. The destination is a real Magic Patterns design, created through the Magic Patterns MCP server.
Magic Patterns renders visual prototypes, not production apps. Local production code will not run there as-is — it must be ported to Magic Patterns' constraints first. recreate-as-react does that port; this skill wires the result into a design.
Keep the scope minimal. Upload only what the user wants to prototype — the specific component or screen and the smallest set of files needed to render it. This is not a tool for mirroring the whole app; a tighter upload compiles more reliably and is faster to iterate on.
Prerequisites
- The Magic Patterns MCP server must be connected (tools prefixed
magic-patterns). If the tools are unavailable, tell the user to install/enable the Magic Patterns plugin or MCP server, and stop. - Magic Patterns MCP usage requires a paid plan. A
Payment Required/ credits error means the user must upgrade atmagicpatterns.com/settings.
Workflow
Step 1 — Pick the minimal scope to prototype
Identify the specific component(s) or screen the user wants to prototype, and the smallest set of files needed to render it. Do not pull in the whole app — keep the upload tight to what the user actually wants to see.
Step 2 — Port to a Magic Patterns-ready file set (run recreate-as-react)
Run the recreate-as-react skill to turn the target into a self-contained React + TypeScript + Tailwind file set (App.tsx, index.tsx, index.css, tailwind.config.js, component files). That skill already targets the Magic Patterns environment and carries the fidelity rules that make the upload look right — follow it in full. In particular it:
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 · 67 lines · 71 tokens per session scan C a94aec7e8678
upload-to-magic-patterns is a skill published in the GitHub repository magicpatterns/agent-plugins (0 stars, last pushed 27d ago), licensed MIT. It adds 71 tokens to every session and 1,349 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…