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 semantic-micro-interactionsgit 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/semantic-micro-interactions)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/semantic-micro-interactions"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/semantic-micro-interactions/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/semantic-micro-interactions"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/semantic-micro-interactions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00096 | $0.01149 |
| Opus 5.5 | $0.00038 | $0.00460 |
| Sonnet 5.5 | $0.00019 | $0.00230 |
| Haiku 4.5 | $0.00010 | $0.00115 |
Grade A, and why
semantic-micro-interactions 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Micro-interactions
Announce at start: "I'm using the humane:semantic-micro-interactions skill to make state changes feel clear without making motion carry the meaning."
A micro-interaction is a bounded response to a meaningful state transition. Start with what changed and what the person needs to understand; motion, highlight, status text, haptics, and sound are possible channels after that decision. An effect with no state change or orientation job is decoration and does not belong in the interaction map.
Quick reference
| Need | Read |
|---|---|
| Pattern selection, interruption, gesture and status guidance | references/patterns.md |
| The interaction-map fields and accessibility invariants | references/contract.md |
Map the transition
For each moment, record:
- The semantic trigger and the before/after states. Use
activate,focus,hover,state-change,validation,completion, orgesture-end; do not make raw DOM events the design contract. - The intent:
acknowledge,confirm,reject,reveal,connect,progress, orsettle. - What already communicates the result without motion or sound. If the answer is nothing, repair the state semantics before animating it.
- The full-motion feedback, its reduced and no-motion substitutions, and every equivalent input route.
- Interruption, cancellation, repetition and rate-limit behavior.
Write the result as an interaction map using references/contract.md. When the
user wants a saved artifact, resolve artifact_path(name, "semantic-micro-interactions", "json"); never assemble a .design path at the
call site. Validate a saved map with python3 scripts/validate_map.py <map.json>.
Hard boundaries
- Use native controls and platform keyboard conventions before custom gesture handling. Hover may enrich; it never reveals required information or the only control.
- A press appearance may begin on pointer-down. Navigation, submission, destructive actions, and persistent changes commit on activation/pointer-up, unless an explicit undo or essential exception makes the alternative safe.
- Dragging has both a keyboard route and a non-dragging single-pointer route. Keyboard support alone does not satisfy the latter.
- Motion never moves focus. A reveal preserves logical focus order, and a status update is announced only when it is actually a status message.
- Non-essential spatial travel, parallax, scale, path and rotation have a reduced-motion substitution. Do not implement reduced motion as a global near-zero duration that leaves vestibular movement intact.
- Reject ambient loops, strobing, repeated shake, and effects that delay the true state. Feedback is interruptible and settles into the actual state.
What ships with it
5 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.
- 1mo ago First seen · 105 lines · 96 tokens per session scan A 546c7f7ba94e
semantic-micro-interactions is a skill published in the GitHub repository glebis/humane-agentic-design (36 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,149 once invoked, about $0.0004 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-11.
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…