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 rijuvashisht/Magneto --skill plan-design-reviewgit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/plan-design-review)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/plan-design-review"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/plan-design-review/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/rijuvashisht/magneto/plan-design-review"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/plan-design-review.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.00000 | $0.00516 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
plan-design-review 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan-design-review — UX / UI Review of the Plan
Role: Senior Designer
Inputs: plan.md
Outputs: appends to plan-reviews.md
Audit actions: plan-design-review.scored, plan-design-review.polished
What This Skill Does
Rates the plan on 6 design dimensions 0-10, explains what a 10 looks like for each, then edits the plan to raise the lowest-scoring dimensions.
Dimensions
- Clarity — Does a first-time user know what to do?
- Hierarchy — Is the most important action most prominent?
- Affordance — Does every interactive element signal its behavior?
- Feedback — Does every action show success/failure/progress?
- Empty states — What does this look like with no data?
- Error states — What does this look like when something breaks?
The Protocol
Step 1: Read plan.md (specifically the UI/UX sections)
Step 2: For each dimension, rate + explain
## Design Review
### Clarity: 6/10
A 10 would: every button label is a verb; every screen has a single primary action.
Current: "Submit" is fine but "Settings" page has 3 primary buttons.
Fix: demote "Reset" and "Export" to secondary style.
### Hierarchy: 4/10
A 10 would: primary action is 2x more prominent than secondary; tertiary actions are in menus.
Current: "Delete Account" and "Save" are styled identically.
Fix: Delete Account becomes text link in a red-bordered section at bottom.
Step 3: AI slop detection
Flag generic-LLM-generated copy:
- "Unlock the power of..."
- "Streamline your workflow..."
- "Revolutionary approach to..."
Rewrite with specific, measurable, human language.
Step 4: Interactive polish (one AskUserQuestion per major choice)
Don't rewrite silently. For each proposed change, ask:
"Delete Account button style change — make it a text link at the bottom of a red-bordered section? (y/n/alt)"
Emit audit: magneto audit add plan-design-review.scored --payload '{"avg":N,"dimensions":{...}}'.
Trigger Phrases
- "design review"
- "ux review"
- "rate the design"
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.
- 11d ago First seen · 63 lines · 0 tokens per session scan A ef8800f6ea86
plan-design-review is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 516 tokens. 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
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
chrome-cdp
Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.
vellum-workspace-theme
Customize the app's visual theme — author design-token overrides (accent, background, surfaces, text, message-bubble colors) in the workspace ui/theme.json, validated by the assistant runtime and applied live to connected clients. Covers the token slots, the all-or-none override groups, the contrast floor, and reading…
vellum-avatar
Customize the assistant's avatar - build a native character, upload an image, or generate one with AI.
ima2-uiux
Design direction discovery and UX judgment for ima2 users. Use for UI/UX direction and design judgment — vague visual briefs, onboarding, empty/error/loading states, layout vocabulary, typography breaks, favicons, logos, and brand identity choices. Pairs with ima2-front: this skill decides the design direction, then…