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 human-avatar/skills-for-humanity --skill s4h-designgit clone --depth 1 https://github.com/human-avatar/skills-for-humanityWrote 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/human-avatar/skills-for-humanity/s4h-design)<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-design"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-design/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/human-avatar/skills-for-humanity/s4h-design"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-design.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.00073 | $0.01239 |
| Opus 5.5 | $0.00029 | $0.00496 |
| Sonnet 5.5 | $0.00015 | $0.00248 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
s4h-design 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design
Applies design thinking to problems of form, function, and fit — finding what people actually need, using constraints productively, shaping through iteration, and cutting to the essential. Diagnoses what kind of design work is needed and applies the right tool.
Which tool fits
| You need to... | Tool |
|---|---|
| Find what people actually need, beneath what they say they want | user-needs |
| Map hard limits versus soft preferences and understand the solution space they define | design-constraints |
| Structure a feedback loop between making and learning | iteration |
| Remove what's unnecessary and find the essential form | simplicity |
Routing Decision
Framing check: Confirm the design situation and the core question before routing. State what you've identified — the object being designed and the problem it needs to solve — in one sentence, then use AskUserQuestion:
-
Question: "I'm reading this as: [your one-sentence framing of the design situation and the core question]. Is that right?"
-
Header: "Framing"
-
Options:
- Yes — proceed — framing is correct
- Adjust — one element is off; user will correct it before you continue
- Reframe — different situation than read; incorporate the correction before proceeding
-
Don't know what the user actually needs, or the stated need feels like a proxy → user-needs
-
Have a list of constraints and need to understand what design space they leave → design-constraints
-
Have a direction but need to test and improve it through cycles → iteration
-
Something exists but feels bloated, cluttered, or over-engineered → simplicity
-
Unclear → user-needs first; most design failures begin with the wrong problem
Confirm Direction
After diagnosing which tool fits, use the AskUserQuestion tool to confirm direction. Construct the question dynamically to include your diagnosis:
- Question: "My read: [diagnosed tool] — [one sentence on why it fits]. How would you like to proceed?"
- Header: "Direction"
- Options:
- Yes, run that tool — Execute the diagnosed skill immediately using the context already provided
- Show all options — List every skill in this category with one-line descriptions
- Quick version — Run a lighter-weight alternative if one exists for this situation
- Re-diagnose — Revisit the situation description for a different read
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 · 88 lines · 73 tokens per session scan A bb6b2718ab79
s4h-design is a skill published in the GitHub repository human-avatar/skills-for-humanity (236 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,239 once invoked, about $0.0003 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
customer-journey-map
Visualize every touchpoint a customer has with a product or service — stages, actions, emotions, pain points, opportunities.
double-diamond
Design problems with two diamond phases: Discover/Define (right problem), Develop/Deliver (right solution).
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
codebase-index
Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.