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/setupnpx skills add glebis/humane-agentic-design --skill setupgit clone --depth 1 https://github.com/glebis/humane-agentic-designWhat 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.00125 | $0.02710 |
| Opus 5 | $0.00063 | $0.01355 |
| Sonnet 5 | $0.00025 | $0.00542 |
| Haiku 4.5 | $0.00013 | $0.00271 |
Grade A, and why
setup 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Announce at start: "I'm using the humane:setup skill to diagnose this machine before changing anything."
Two jobs, in this order: find out what is actually wrong, then fix only what the user agrees to fix. Never the other way round — a setup flow that installs first and reports afterwards is one that installs things nobody wanted.
scripts/humane_setup.py doctor # read-only: config + every check + the fix for each gap
scripts/humane_setup.py config # show resolved configuration and where each value came from
scripts/humane_setup.py config --set language=ru [--scope project]
scripts/humane_setup.py settings # what each setting means
doctor writes nothing, installs nothing, and never asks for a key. It exits 1
only on a genuinely blocking gap; missing optional pieces exit 0, because most
of the cycle works without them.
Configuration
The settings below, resolved highest-precedence first: project humane.json >
~/.humane/config.json > HUMANE_* environment > built-in default. doctor
and config print the source beside every value, so "why is it using that
path?" is always answerable.
| Setting | Default | What depends on it |
|---|---|---|
corpus_root |
~/jtbd |
where jtbd writes; every later skill reads it |
token_base |
~/design-tokens/base.tokens.json |
the global brand a project layers over |
image_backend |
auto |
which generator brand-illustrate shells out to |
task_export |
none |
where nielsen-heuristics files findings (linear, beads, none) |
language |
en |
the language skills speak; captured evidence is never translated |
design_tool |
auto |
editable design-file backend for humane:prototype (auto · pencil · none). auto uses one when the host exposes it and stays on the file ladder when it does not. Not verifiable by the doctor — it is a host capability, not a binary on PATH |
artifact_root |
.design |
where generated artifacts land — prototypes, specimens, boards, illustrations, walks, saved reviews — each named for the skill that made it (.design/prototype-dashboard.html). Separate from corpus_root because a corpus is usually personal and global while an artifact belongs beside the project. A relative value resolves against the project directory, never the working directory. See references/paths.md for the full table |
browser_tool |
auto |
what drives a live interface in walkthrough driven mode (and the skills that cite its procedure). auto resolves the ladder in walkthrough/references/driven.md: agent-browser CLI → Playwright MCP → host browser tools → the user drives. Set explicitly to pin a rung |
What ships with it
6 files 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.
- 3d ago First seen · 199 lines · 125 tokens per session scan A d829114f2615
setup is a skill published in the GitHub repository glebis/humane-agentic-design (27 stars, last pushed 24d ago), licensed MIT. It adds 125 tokens to every session and 2,710 once invoked, about $0.0006 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…