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/guillermoscript/lms-front/ui-evidencenpx skills add guillermoscript/lms-front --skill ui-evidencegit clone --depth 1 https://github.com/guillermoscript/lms-frontWrote 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/guillermoscript/lms-front/ui-evidence)<a href="https://agentmods.dev/skills/guillermoscript/lms-front/ui-evidence"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/ui-evidence.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 | $0.00121 | $0.00898 |
| Opus 5 | $0.00060 | $0.00449 |
| Sonnet 5 | $0.00024 | $0.00180 |
| Haiku 4.5 | $0.00012 | $0.00090 |
Grade A, and why
ui-evidence 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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Evidence — before/after screenshots and a verification GIF
Reviewers weigh a before/after pair far more than a description of what changed, and the GIF comment is what tells them "this needs your visual sign-off". For any user-visible change this evidence is mandatory, not decorative.
Chrome is a single shared resource — never delegate it. All browser steps here (screenshots, GIF recording, uploads) run in the main agent via the claude-in-chrome tools; parallel subagents fighting over one browser serialize badly and corrupt each other's recordings. If several tasks need Chrome, queue their browser steps and do them one at a time at the end.
1. Before-captures — do this BEFORE touching the code
The only moment the "before" state exists is before implementation — once the change lands, it's gone. As soon as it's known that a change touches UI:
- Start (or find) the locally running app — check for a
runskill or repo docs for the start command and local URL/basePath conventions. - Open the affected screen(s) in Chrome and screenshot each
(
mcp__claude-in-chrome__computer, screenshot action), saved asissue-<N>-before-<screen>.png(orbefore-<screen>.pngif there's no issue number). - If the local app isn't running and starting it is disruptive right now, note that "before" captures were skipped and why — don't silently drop them.
2. Verification GIF + after-shots — after implementing
- Drive the changed flow end-to-end in the running app (the
verifyskill covers how to exercise it; this skill covers how to record it). - Record the drive with
mcp__claude-in-chrome__gif_creator: start capture before the first action, capture extra frames before and after each step so playback is smooth, and name the file after the work (e.g.issue-<N>-verification.gif). Save it somewhere durable and note the path. - Take "after" screenshots of the same screens captured in step 1
(
issue-<N>-after-<screen>.png) so the PR can show matched before/after pairs — same screen, same viewport, ideally same scroll position.
What ships with it
1 file 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.
- 4d ago First seen · 71 lines · 121 tokens per session scan A d67ad38a780b
ui-evidence is a skill published in the GitHub repository guillermoscript/lms-front (25 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 898 once invoked, about $0.0006 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-30.
Other skills, from other repositories
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
apple-design
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…
add-landing-template
Add a new org landing-page template to the ClassroomIO monorepo. Use when the user asks to "create/add a new landing template", "add a new template like X to the org landing pages", "build a new theme for the org landing page", or hands over a design reference (image, URL, prototype) for a new landing visual style.
animation-vocabulary
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and…
prototype
Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.