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 glebis/humane-agentic-design --skill design-frameworksgit 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/design-frameworks)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/design-frameworks"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/design-frameworks/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/glebis/humane-agentic-design/design-frameworks"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/design-frameworks.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.00146 | $0.01769 |
| Opus 5.5 | $0.00058 | $0.00708 |
| Sonnet 5.5 | $0.00029 | $0.00354 |
| Haiku 4.5 | $0.00015 | $0.00177 |
Grade A, and why
design-frameworks 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Frameworks
Announce at start: "I'm using the humane:design-frameworks skill to fit this implementation to the project's existing design system without changing the product decision above it."
This skill is an implementation adapter. It translates a settled-enough design decision into the components, patterns, tokens, themes, templates, and checks an existing system actually provides. It does not decide what the product should be.
The Humane method stays above every preset:
job → evidence → concept → prototype → review → learning
A preset may report that the system cannot express the accepted concept. It may not silently alter the job, acceptance criteria, content hierarchy, interaction model, or prototype to make the available components look sufficient.
Quick Reference
| Need | Read |
|---|---|
| Preset profiles, selection, and fallback behavior | references/presets.md |
| Common objects, capability rules, fit-plan and finding shapes | references/contract.md |
| Astryx native CLI/API commands and write boundaries | references/astryx.md |
| shadcn registry, CLI/MCP, and source-ownership boundaries | references/shadcn.md |
| Storybook manifests/MCP as a project-local catalog and test overlay | references/storybook.md |
Read only the selected preset reference. Read contract.md when producing a
machine-readable manifest, fit plan, operation receipt, or validation result.
1. Establish the implementation brief
Before touching the framework, name the immutable inputs you are fitting:
- the job or outcome reference;
- the evidence references supporting it;
- the accepted concept and acceptance criteria;
- the prototype or existing implementation being fitted;
- unresolved decisions and review findings that remain open.
References are enough; do not copy the whole Humane corpus into an adapter object. If these inputs do not exist, ordinary framework help can still proceed, but label Humane traceability Not available. Never invent research or claim that a framework-compliant build has validated the product idea.
What ships with it
12 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.
- agents/openai.yaml 293 B
- references/adapter-contract.schema.json 11 KB
- references/astryx.md 3.5 KB
- references/contract.md 3.3 KB
- references/presets.md 2.7 KB
- references/shadcn.md 2.0 KB
- references/storybook.md 1.7 KB
- scripts/validate_fixtures.py 12 KB runs code
- tests/fixtures/astryx.discovery.json 4.7 KB
- tests/fixtures/shadcn.discovery.json 4.4 KB
- tests/fixtures/storybook.discovery.json 4.8 KB
- tests/test_contract.py 3.9 KB runs code
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 · 173 lines · 146 tokens per session scan A c2d8770ded70
design-frameworks is a skill published in the GitHub repository glebis/humane-agentic-design (36 stars, last pushed today), licensed MIT. It adds 146 tokens to every session and 1,769 once invoked, about $0.0006 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-09-05.
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…