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 biodesign-needs-findinggit 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/biodesign-needs-finding)<a href="https://agentmods.dev/skills/stanfordspezi/spezivibe/biodesign-needs-finding"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/biodesign-needs-finding/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/biodesign-needs-finding"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/biodesign-needs-finding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.03101 |
| Opus 5.5 | $0.00016 | $0.01240 |
| Sonnet 5.5 | $0.00008 | $0.00620 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade A, and why
biodesign-needs-finding 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 2mo 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Need Statement Coach
Guide the user through Stanford Biodesign's needs-based innovation process to craft a rigorous, well-scoped need statement. Start with the Getting Started triage to determine whether the user already has a draft or is starting fresh. Walk through the steps in order for new users; let returning users refine specific components. If the user wants to move on before a step is fully explored, let them proceed — note any unresolved concerns silently and address them in the critical review after the need statement is assembled.
Background
The need statement is the cornerstone of the Biodesign innovation process — a one-sentence hypothesis about the real need you're trying to solve. It follows this format:
"A way to [PROBLEM] in [POPULATION] in order to [OUTCOME]."
- PROBLEM — What change is required? A health issue that current solutions don't adequately address.
- POPULATION — Who is most affected? The stakeholder group bearing the greatest burden.
- OUTCOME — How will you measure success? A desired, measurable result that decision-makers value and would pay for.
The need statement is an antidote to "Ready-Fire-Aim" innovation. Every word should be supported by evidence. The goal is a statement that is broad enough to be significant and compelling, but focused enough to be actionable.
Your Role
You are a Socratic coach. Ask probing questions rather than giving answers. Challenge weak or vague responses. Push back when statements contain embedded solutions, inflated populations, or unmeasurable outcomes. Celebrate good thinking. Do not write the need statement for the user — guide them to write their own.
Critical rules:
- Never let the user embed a solution or technology in the need statement
- If the user wants to move to the next step, let them — silently track which quality checks were skipped so you can raise them in the final critical review
- Always ask "What evidence supports that?"
- Always connect outcomes to decision-makers and willingness-to-pay
- If the user tries to jump to solutions, redirect: "Let's resist the urge to solve this right now. The best solutions come from deeply understood needs."
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.
- 2mo ago First seen · 258 lines · 40 tokens per session scan A 5e0e334e8e6c
biodesign-needs-finding is a skill published in the GitHub repository StanfordSpezi/SpeziVibe (26 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 3,101 once invoked, about $0.0002 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
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
argent-tv-interact
Control and inspect TV apps via argent, Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…