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.
git clone --depth 1 https://github.com/MadAppGang/magusWrote 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/plugins/madappgang/magus/designer)<a href="https://agentmods.dev/plugins/madappgang/magus/designer"><img src="https://agentmods.dev/badge/plugins/madappgang/magus/designer/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/plugins/madappgang/magus/designer"><img src="https://agentmods.dev/badge/plugins/madappgang/magus/designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
designer 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 3d 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.
What it actually says
{
"name": "designer",
"version": "0.11.0",
"description": "UI design validation. Compares a rendered screen against its reference by pixel diff, then reviews the result for spacing, hierarchy and design-system consistency.",
"author": {
"name": "Jack Rudenko",
"email": "[email protected]",
"company": "MadAppGang"
},
"license": "MIT",
"keywords": [
"ui",
"design",
"design-review",
"pixel-diff",
"accessibility",
"usability",
"vision-model",
"artboards",
"design-tokens",
"design-system",
"style-guide"
],
"category": "design",
"dependencies": [
{
"name": "claudish",
"version": "^2.0"
}
],
"skills": [
"./skills/compare",
"./skills/ui-analyse",
"./skills/design-references",
"./skills/ui-style-format",
"./skills/browser-use-integration",
"./skills/review-services"
],
"compatibility": {
"claudeCode": ">=0.1.0"
}
}
What it installs
The manifest is a name and a version. 6 skills, 3 commands, 2 agents travel with it, and installing the plugin installs all of them — 579 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill review-services A 48 tokens
- Skill ui-analyse A 48 tokens
- Skill browser-use-integration A 39 tokens
- Skill compare C 27 tokens
- Skill ui-style-format A 41 tokens
- Skill design-references A 39 tokens
- Command review A 35 tokens
- Command ui A 33 tokens
- Command create-style A 45 tokens
- Agent review A 107 tokens
- Agent ui A 117 tokens
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.
- 3d ago Changed b9d7989d12fd
- 20d ago Changed 327f5d9e0ef3
- 22d ago Changed cc4a78e04698
- 23d ago Changed d99be7ba30c9
- 1mo ago Changed · +1 lines 97126c2fde7c
- 1mo ago Changed 550323040c7a
- 1mo ago Changed c71a47eb01f7
- 1mo ago First seen · 42 lines scan A 67f67913f50a
designer is a plugin published in the GitHub repository MadAppGang/magus (13 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
accessibility-compliance
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design.
dotnet-coverage-kit
Characterization-test backfill and spec-test enforcement for .NET services. Deterministic C0/C1 measurement via dotnet-coverage, with a checked-in manifest that explains every inclusion and exclusion.
a11y-audit
Full accessibility audit with WCAG compliance checking.
design-compare
Compare Figma designs against implementation screenshots with interactive HTML reports.
mockup-fidelity
Validate that an implemented React or React Native UI faithfully reproduces a reference mockup, then update the code to close every gap, by measuring the rendered tree rather than eyeballing it or reading source. Treats the mock as the source of truth, inventories every frame including the modals and states the named…
be-my-witness
Validate a UI screenshot against what a test expected and against a design mock, returning a pass/fail gate plus severity-ranked findings. Runs a deterministic pre-scan first (is this evidence, did the surface settle, are the two framings even comparable), crops and zooms rather than judging a full-page thumbnail…