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 skills add rustfs/console --skill ui-auditgit clone --depth 1 https://github.com/rustfs/consoleWrote 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/rustfs/console/ui-audit)<a href="https://agentmods.dev/skills/rustfs/console/ui-audit"><img src="https://agentmods.dev/badge/skills/rustfs/console/ui-audit/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/rustfs/console/ui-audit"><img src="https://agentmods.dev/badge/skills/rustfs/console/ui-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00097 | $0.02661 |
| Opus 5.5 | $0.00039 | $0.01064 |
| Sonnet 5.5 | $0.00019 | $0.00532 |
| Haiku 4.5 | $0.00010 | $0.00266 |
Grade A, and why
ui-audit 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Audit
Operating Mode
Treat the request as implementation work unless the user asks for analysis only. Read local instructions first, preserve unrelated changes, and keep edits surgical. Do not create project summary documents or reports unless explicitly requested.
In this repository, read skills/rustfs-console-design-guide/SKILL.md before auditing or changing Console UI. Use that guide as the source of design decisions; use this skill for audit execution, browser validation, evidence capture, and verification.
If the user asks to pull latest, do it before editing after checking git status. If local unrelated work is present, preserve it and avoid destructive git commands.
Classify The Surface
Before scanning, identify the primary UI type and adjust emphasis:
- Operational apps: prioritize density, tables, forms, keyboard flow, data states, batch actions, and predictable navigation.
- Landing/product sites: prioritize first viewport, real visual assets, responsive hero composition, contrast, content hierarchy, and scroll rhythm.
- Developer/docs sites: prioritize reading flow, code block overflow, navigation state, search, anchors, and dark theme.
- Interactive tools/games: prioritize canvas/scene nonblank state, controls, motion, hit targets, and viewport fit.
- Component libraries/migrations: prioritize primitive usage, wrapper boundaries, design tokens, API consistency, and regression patterns.
Baseline
- Read project guidance: local instructions, package scripts, existing component patterns, theme config, and design-system conventions.
- Prefer existing wrappers and utilities. Do not edit base UI primitives directly unless explicitly required; fix usage sites or create wrappers.
- Start or reuse the local dev server. Use Docker Compose only when the app needs it.
- Fetch current UI guidance when available, especially:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
- Define target flows: first screen, navigation shell, forms, dialogs, tables/lists, media, upload flows, theme switch, and one mobile breakpoint.
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.
- 1mo ago First seen · 144 lines · 97 tokens per session scan A f33639e6f9f3
ui-audit is a skill published in the GitHub repository rustfs/console (198 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 2,661 once invoked, about $0.0004 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-30.
Other skills, from other repositories
files-sdk
Use files-sdk to add file storage to a TypeScript/JavaScript app with a unified API across 49 adapters (S3, R2, GCS, Azure, Vercel Blob, the local filesystem, and more). Triggers when the user wants to upload/download/list/search/move/delete/copy files, generate presigned URLs, do multipart or resumable uploads, range…
s3-minio-content-type-xss
Exploit public bucket Content-Type override for stored XSS on target origin.
terraform-minio
Author, plan, and safely apply Terraform for MinIO and S3-compatible object storage using the aminueza/minio provider. Use this skill whenever the user works with the MinIO Terraform provider, writes or reviews any minio resource or data source (minios3bucket, minioiamuser, minioiampolicy, minioiamserviceaccount…
agent-fs
Use when the user wants to store, retrieve, search, or manage files in agent-fs — an agent-first filesystem backed by S3. Triggers on: "save this to agent-fs", "find that file", "store this document", "search agent-fs", "list my files", "show version history", "revert file", "set up agent-fs", "get a signed url"…
minio-aiops
Use this skill whenever the user needs to operate or diagnose MinIO object storage — explain why the cluster is filling up or refusing writes (capacityrca), find publicly exposed buckets and hygiene gaps (bucketexposureaudit), find storage that lifecycle/ILM should be reclaiming but isn't, including noncurrent…
minio
Operate Joel's MinIO legacy/rollback services and S3-compatible object storage checks. Use for MinIO, ASUSTOR MinIO CE, custom Docker/Compose MinIO, Convex MinIO rollback, and MinIO-vs-Garage questions. For canonical local Convex object storage, use Garage/local-convex.