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/stuartshields/claude-setup/vibe-usernpx skills add stuartshields/claude-setup --skill vibe-usergit clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/stuartshields/claude-setup/vibe-user)<a href="https://agentmods.dev/skills/stuartshields/claude-setup/vibe-user"><img src="https://agentmods.dev/badge/skills/stuartshields/claude-setup/vibe-user.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.01171 |
| Opus 5 | $0.00018 | $0.00585 |
| Sonnet 5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
vibe-user 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 3d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: vibe-user
When to Use
Use this skill after building a feature, when you want honest UX feedback, or for periodic usability review. Invoke with /vibe-user [URL] to test a specific page, or /vibe-user and provide the URL when prompted.
Use $ARGUMENTS as the target URL. If empty, ask the user what URL to test.
Do NOT fix or modify anything. This skill reports only.
Role
You are a user with no prior knowledge of this app. You don't know where things are, what the terminology means, or what the expected flows are. You discover everything by exploring. You are not an engineer reviewing code -you are a person trying to use the product to get something done.
Method
Step 1: Navigate and Orient
Open the URL. Take a snapshot. Answer these questions from a first impression:
- What is this page? What app is this?
- What can I do here? Are the available actions obvious?
- What's confusing at first glance? Any jargon, unclear labels, or ambiguous icons?
Step 2: Explore Every Reachable Page
Visit every page reachable via navigation (menus, links, buttons). For each page, document:
| Aspect | What to Record |
|---|---|
| Page name / route | URL and what you'd call this page as a user |
| Purpose | What this page does (your observation, not what you think it should do) |
| Usability issues | Friction, unclear labels, missing feedback, unexpected behaviour |
| Interaction problems | Buttons that don't respond, forms without validation feedback, dead ends, broken flows |
| Accessibility quick checks | Can you tab through interactive elements? Are buttons and links labelled? Is focus visible? |
Use browser_snapshot to understand page structure and find interactive elements. Use browser_take_screenshot to capture visual evidence of issues.
Step 3: Test Core Flows
Identify the 3-5 most important user flows (signup, login, primary action, search, settings, etc.) and walk through each end-to-end. For each flow, note:
- Where you got stuck or confused
- Where you had to guess what to do next
- Where the app gave no feedback after an action
- Where the app surprised you (good or bad)
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.
- 3d ago First seen · 79 lines · 36 tokens per session scan A 0167f6b6f7d9
vibe-user is a skill published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,171 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
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
ce-polish
Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…
a11y-audit
../../../engineering-team/a11y-audit/skills/a11y-audit/SKILL.md.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…