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 Tiltely/lens/plugin install lensWrote 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/tiltely/lens/usability)<a href="https://agentmods.dev/skills/tiltely/lens/usability"><img src="https://agentmods.dev/badge/skills/tiltely/lens/usability/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/tiltely/lens/usability"><img src="https://agentmods.dev/badge/skills/tiltely/lens/usability.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.00068 | $0.00901 |
| Opus 5.5 | $0.00027 | $0.00360 |
| Sonnet 5.5 | $0.00014 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
usability 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Lens of Usability
Read first: ${CLAUDE_PLUGIN_ROOT}/core/protocol.md and ${CLAUDE_PLUGIN_ROOT}/core/dossier.md. Dossier rules: read it, skip answered questions WITH skip lines, append your outputs.
Mode selection
- Explicit argument wins ("audit" / "design").
- Otherwise infer: planning a new page/flow → design; reviewing one already built → audit. Confirm your inference in one line.
Question battery — design mode
Tier 1 — framing (always)
- Walk me through how the user ACTUALLY ends up on this page — from where, in what state of mind, on what device? (If the walk-through stalls, that IS the finding.)
- What does the user want to leave with — and how many steps does that take today?
Tier 2 — flow and navigation
- From this page, where can the user go next — and is every likely "next" reachable without using the browser back button?
- What is missing: is there an action users will look for here that has no button? (The test: narrate the user's inner monologue — "ok, and now how do I…?")
- For each async action: what does the user see while waiting, on success, and on failure? (loading / success feedback / error recovery — name all three.)
- First-time user vs returning user: do both make sense of this page? Does the first-timer need an empty state that teaches?
Tier 3 — reach (only when triggered)
- Real users speak multiple languages → do we need i18n here, and in which languages? Who maintains translations? (Per Tiltely: neutral tú-form Spanish when Spanish.)
- Feature exists on web AND mobile → does the flow match on both? Intentional divergences documented? (This question is the seed of the future parity lens.)
- Forms → can it be completed one-handed on a phone? Are inputs the right keyboard type?
Output contract — design mode
decisions[] · risks[] · open[] · blast-radius notes (e.g., "i18n decision touches email templates too"). Append to dossier.
Question battery — audit mode (critique the built flow)
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 First seen · 78 lines · 68 tokens per session scan A 2dab1246f315
usability is a skill published in the GitHub repository Tiltely/lens (5 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 901 once invoked, about $0.0003 per session on Opus 5.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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.