Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slamb2k/mad-skills/plugin install mad-skillsWrote 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/slamb2k/mad-skills/wright)<a href="https://agentmods.dev/skills/slamb2k/mad-skills/wright"><img src="https://agentmods.dev/badge/skills/slamb2k/mad-skills/wright.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.1 | $0.00055 | $0.02016 |
| Opus 5 | $0.00028 | $0.01008 |
| Sonnet 5 | $0.00011 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
wright 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 6d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wright - Plugin Updater
When this skill is invoked, IMMEDIATELY output the banner below before doing anything else.
Pick ONE tagline at random — vary your choice each time.
CRITICAL: Reproduce the banner EXACTLY character-for-character, including the diagonal / glyph before the name.
{tagline}
/$$ /$$ /$$ /$$$$$$$ /$$$$$$ /$$$$$$ /$$ /$$ /$$$$$$$$
/$$/| $$ /$ | $$| $$__ $$|_ $$_/ /$$__ $$| $$ | $$|__ $$__/
/$$/ | $$ /$$$| $$| $$ \ $$ | $$ | $$ \__/| $$ | $$ | $$
/$$/ | $$/$$ $$ $$| $$$$$$$/ | $$ | $$ /$$$$| $$$$$$$$ | $$
/$$/ | $$$$_ $$$$| $$__ $$ | $$ | $$|_ $$| $$__ $$ | $$
/$$/ | $$$/ \ $$$| $$ \ $$ | $$ | $$ \ $$| $$ | $$ | $$
/$$/ | $$/ \ $$| $$ | $$ /$$$$$$| $$$$$$/| $$ | $$ | $$
|__/ |__/ \__/|__/ |__/|______/ \______/ |__/ |__/ |__/
Taglines:
- 🔧 Tightening every bolt in the toolbox...
- 🛠️ The wright is in — fixing up your plugins!
- ⚙️ Refitting the fleet, one plugin at a time...
- 🪚 A little maintenance never hurt anybody!
- 🧰 Checking the workshop for stale tools...
- 🔩 Bringing everything up to spec!
- 🏗️ Overhaul in progress...
- 📐 Measure twice, update once!
Output Formatting
After the banner, display parsed input:
┌─ Input ────────────────────────────────────────
│ Target: {plugin name or "all installed"}
│ Flags: {parsed flags or "none"}
└────────────────────────────────────────────────
Pre-flight results:
── Pre-flight ───────────────────────────────────
✅ {dep} {version or "found"}
⚠️ {dep} not found → {fallback detail}
❌ {dep} missing → stopping
──────────────────────────────────────────────────
Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
Update installed Claude Code plugins by orchestrating the claude plugin
CLI — the CLI does the real work (refreshing marketplace sources, including
the GCS-backed official one, resolving versions, populating the cache); this
skill adds only what the CLI itself lacks on its own: updating everything in
one call, and targeting one plugin by fuzzy name instead of its exact
plugin@marketplace id.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 180 lines · 55 tokens per session scan A 8df58805691d
wright is a skill published in the GitHub repository slamb2k/mad-skills (5 stars, last pushed 17d ago), licensed MIT. It adds 55 tokens to every session and 2,016 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…