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/stefan-stepzero/shipkit/shipkit-ux-auditnpx skills add stefan-stepzero/shipkit --skill shipkit-ux-auditgit clone --depth 1 https://github.com/stefan-stepzero/shipkitWrote 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/stefan-stepzero/shipkit/shipkit-ux-audit)<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-ux-audit"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-ux-audit.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.00036 | $0.04366 |
| Opus 5 | $0.00018 | $0.02183 |
| Sonnet 5 | $0.00007 | $0.00873 |
| Haiku 4.5 | $0.00004 | $0.00437 |
Grade A, and why
shipkit-ux-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 5d 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-ux-audit - Lightweight UX Guidance
Purpose: Ensures UI patterns stay consistent and user-friendly across the application by providing UX guidance based on general best practices, existing patterns in the project, and optional user-specified personas (e.g., ADHD-friendly, elderly users).
When to Invoke
User triggers:
- "What's the best UX pattern for this?"
- "How should this UI work?"
- "UX guidance for [component]"
- "Make this accessible"
- "Check UX consistency"
Before:
- Building new UI components
- Implementing forms, modals, toggles, lists, buttons
- Creating user interactions
During:
- Reviewing implemented UI
- Refining user experience
- Fixing UX inconsistencies
Prerequisites
Optional but helpful:
- Existing patterns documented:
.shipkit/codebase-index.json - Architecture decisions:
.shipkit/architecture.json - Stack info:
.shipkit/stack.json
No prerequisites required - Can provide general guidance even for new projects.
Process
Completion Tracking (MANDATORY)
After confirming what the user is building (Step 1), create tasks:
TaskCreate: "Read existing context (codebase-index, ux-decisions, stack)"TaskCreate: "Explore actual UI components (2 parallel agents)"TaskCreate: "Generate UX guidance (terminal output)"TaskCreate: "Log decision to ux-decisions.json + update summary counts"TaskCreate: "Identify and log gaps + update totalGaps count"TaskCreate: "Suggest next steps"
Rules:
- Terminal output (Step 4) is NOT the finish line — JSON persistence (Steps 5-6) must follow
TaskUpdatethe JSON logging task tocompletedonly after verifying ux-decisions.json was written with updated summary counts- If auditing existing UI, the gaps task is required, not optional
- Do NOT present "done" until both the terminal guidance AND the JSON file writes are confirmed
Step 1: Confirm What User is Building
Before providing guidance, ask 2-3 questions:
What ships with it
2 files 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.
- 5d ago First seen · 535 lines · 36 tokens per session scan A 6a5f4b75fd40
shipkit-ux-audit is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 4,366 once invoked, about $0.0002 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-31.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
golden-rss
Use when testing the rss golden build.
golden-chat-topics
Use when testing the goldenchattopics golden build.
golden-chat-single
Use when testing the goldenchatsingle golden build.
golden-rss-empty
Use when testing the empty rss golden build.
igce-builder-cr
Trigger for: cost-reimbursement IGCE, CR cost estimate, CPFF, CPAF, CPIF, cost-plus estimate, BAA estimate, fixed-fee analysis, award-fee analysis, incentive-fee analysis, proposed CR rate validation, cost-pool buildup, share-ratio scenario, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable…