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/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/mockup-fidelity)<a href="https://agentmods.dev/plugins/fledgeling-co/fledgeling-plugins/mockup-fidelity"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/mockup-fidelity/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/fledgeling-co/fledgeling-plugins/mockup-fidelity"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/mockup-fidelity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mockup-fidelity 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 1mo 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": "mockup-fidelity",
"description": "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 screens open, and inverts the burden of proof so a difference is a defect until an external citation proves it intentional. Its distinguishing feature is that it refuses to certify a property its browser engine cannot actually measure: a runtime preflight sets each declaration through a real stylesheet rule and reads it back with two different sentinels, and any detector class that fails is reported as inconclusive with the engine's own reason string instead of quietly agreeing. On the sanctioned engine nine classes fail that probe, including box-shadow and placeholder colour, the two properties most often silently wrong. Diffs structure before styling, pairs text-less icons and dividers by bounding box, crops and pixel-diffs every paired element, and emits a present/divergent/absent ledger, a functional-gaps document, and a three-valued exit code where inconclusive is neither a pass nor a failure. Carries a second measurement engine for native macOS, Electron and web-view targets, and for the classes a browser engine reports nothing for: it drives the proctor skill to read the accessibility tree, the compositor's resolved layer values and frame trustworthiness, establishing that engine's own capability tier before a style finding may claim anything. Use it when someone asks whether a build matches its design, to pixel-match a screen, to audit UI fidelity after a port or migration, or to find what a mock contains that was never built.",
"version": "3.4.2",
"author": {
"name": "Fledgeling",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 338 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago Changed a2722d4b18ce
- 1mo ago First seen · 10 lines scan A 9a56eb97fac2
mockup-fidelity is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), 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-09-04.
Other plugins, from other repositories
accessibility-compliance
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design.
stuntdouble
Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.
muki-ai-plugins marketplace
Muki's Claude Code plugins — project lore knowledge base, test quality review, visual regression testing, AI session review, Jev-powered web search, a virtual pet that grows from your Claude Code work, and world news under your prompt.
e2e
E2E test triage, debugging, and fix implementation toolkit.
meticulous
Agent skills for Meticulous visual regression testing — review test runs, investigate replays, debug diffs. Also connects the hosted Meticulous MCP server.
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.