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/glebis/humane-agentic-design/using-humanenpx skills add glebis/humane-agentic-design --skill using-humanegit clone --depth 1 https://github.com/glebis/humane-agentic-designWrote 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/glebis/humane-agentic-design/using-humane)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/using-humane"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/using-humane.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.00157 | $0.01415 |
| Opus 5 | $0.00078 | $0.00707 |
| Sonnet 5 | $0.00031 | $0.00283 |
| Haiku 4.5 | $0.00016 | $0.00142 |
Grade A, and why
using-humane 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using humane
Announce at start: "I'm using the humane:using-humane skill to route this to the skill that owns it."
Scope
This skill routes design work. It does not claim authority over unrelated tasks — a bug fix, a deploy, or a shell question has no humane owner, and routing one here is a false positive. If nothing below matches, say so and move on rather than stretching a design skill over a non-design task.
The two questions it answers
"Where do I start?" — match the intent to an entry point (table below).
"I just finished X, what now?" — do not recall the cycle from memory. Ask the graph:
python3 scripts/graph.py --from layout-rules # what it hands to, and when
python3 scripts/graph.py --to ux-writing # who hands in here, and when
python3 scripts/graph.py # the whole graph
python3 scripts/graph.py --mermaid # the graph as a diagram
The script reads the frontmatter of every skill in the plugin. It is stdlib-only and has no dependencies, so it runs anywhere the plugin is checked out.
Entry points
| The user says | Start with | Not with |
|---|---|---|
| "something's missing / nothing works / fresh machine" | humane:setup |
anything else — it diagnoses first |
| "what should I build", "what are people hiring this for" | humane:jtbd |
a review skill; there is nothing to review yet |
| "mock this up", "show me the flow", "wireframe this" | humane:prototype |
humane:design-tokens — the structure is not settled yet |
| "we need a brand / an identity" | humane:brandkit |
humane:design-tokens — the tokens do not exist yet |
| "set up tokens", "compile to CSS", "check contrast" | humane:design-tokens |
humane:layout-rules, which only flags the pair |
| "pick a font", "does this font have Cyrillic" | humane:type-specimen |
humane:design-tokens, until a family is chosen |
| "generate on-brand images" | humane:brand-illustrate |
humane:brandkit, which explores rather than produces |
| "what should this button say", "rewrite this error" | humane:ux-writing |
— |
| "how does this land", "test this tagline" | humane:respondent-panel |
humane:persona-review — strangers, not experts |
| "review this PRD as an engineer / investor" | humane:persona-review |
humane:respondent-panel — experts, not strangers |
| "review this UI", "check this dashboard" | humane:layout-rules |
— |
| "usability audit", "heuristic evaluation" | humane:nielsen-heuristics |
— |
| "can someone actually complete this", "test this flow" | humane:walkthrough |
humane:nielsen-heuristics — attempt, not inspect |
| "what's the transformation" | humane:before-after |
— |
| "review this properly", "full review", "holistic audit" | humane:review |
any single domain skill |
What ships with it
1 file 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.
- 4d ago First seen · 92 lines · 157 tokens per session scan A 1767eff7199b
using-humane is a skill published in the GitHub repository glebis/humane-agentic-design (27 stars, last pushed 25d ago), licensed MIT. It adds 157 tokens to every session and 1,415 once invoked, about $0.0008 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
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…