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 StanfordSpezi/SpeziVibe --skill digital-health-ux-planninggit clone --depth 1 https://github.com/StanfordSpezi/SpeziVibeWrote 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/stanfordspezi/spezivibe/digital-health-ux-planning)<a href="https://agentmods.dev/skills/stanfordspezi/spezivibe/digital-health-ux-planning"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/digital-health-ux-planning/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/stanfordspezi/spezivibe/digital-health-ux-planning"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/digital-health-ux-planning.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.00027 | $0.00738 |
| Opus 5 | $0.00014 | $0.00369 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
digital-health-ux-planning 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 12d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Planner
Plan user experience flows for digital health products without assuming a specific client technology.
When to Use
Use this skill when you need to:
- design end-to-end journeys for patients, participants, clinicians, or coordinators
- plan onboarding and consent-adjacent flows
- structure recurring health tracking or task completion workflows
- think through engagement, motivation, and accessibility
Working Style
Begin with the people, decisions, and moments that matter. Do not start with screens.
Clarify:
- primary users
- core jobs to be done
- highest-friction moments
- what users need to understand, decide, or complete
- what success looks like for both the user and the program
Planning Framework
1. User Segments
Identify:
- primary users
- secondary users
- staff or caregiver roles
- user constraints such as health literacy, accessibility needs, fatigue, or limited time
2. Core Journeys
Map the main flows in plain language, for example:
- discover and enroll
- learn what the product is for
- provide consent or required acknowledgements
- complete the first meaningful task
- return for ongoing use
- review progress or history
- get help or recover from confusion
3. Onboarding
Plan what users need at the beginning:
- orientation and trust-building
- account setup if applicable
- permissions or access requests only when needed
- profile or baseline setup
- first action that creates value quickly
Challenge any onboarding flow that asks for too much too soon.
4. Day-to-Day Workflow
Describe the recurring experience:
- what prompts the user to return
- what they see first
- what they are expected to do
- how completion and progress are communicated
- what happens when they skip, fall behind, or lose context
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.
- 12d ago First seen · 131 lines · 27 tokens per session scan A c298c4146e20
digital-health-ux-planning is a skill published in the GitHub repository StanfordSpezi/SpeziVibe (24 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 738 once invoked, about $0.0001 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
frontend-design-landing-page
Marketing landing page and conversion-focused product page reference. Use this skill when building hero sections, feature grids, pricing pages, testimonials, CTAs, footers, navigation bars, or any public-facing marketing surface. Covers a warm, professional, developer-friendly design language (cream backgrounds…
frontend-design-saas
S-tier SaaS dashboard and product UI reference. Use this skill when building application shells, data tables, settings panels, billing pages, dashboards, auth flows, admin tools, or any internal/customer-facing SaaS product UI. Inspired by Stripe, Linear, Vercel, Airbnb, Notion. Covers neutral-led design tokens…
argent-lens
Propose multiple visual design variants for on-screen elements and let the human pick in the Argent Lens window. Use when the user asks for design alternatives / options / A-B choices for a screen or component, or any time you have produced more than one candidate look for an element and want a human decision before…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
create-openbitfun-cinematic-wallpaper-skin
Apply the cinematic animated-wallpaper style recipe to a OpenBitFun Appearance skin. Use after loading the parent create-openbitfun-skin Skill when the user provides animated character artwork and wants a host-managed video background, source-derived glass materials, image-led cards, illustrated dialogs, reproducible…
create-openbitfun-skin
Inspect the current OpenBitFun Appearance contract and author, repair, package, or validate sparse .openbitfun-appearance skins. Use when Codex needs to discover registered scenes/components/parts/states/facets, check Style IR properties or renderer tokens, initialize or inspect a package, diagnose import failures…