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 sound-effectsgit 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/sound-effects)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/sound-effects"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/sound-effects/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/sound-effects"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/sound-effects.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.00104 | $0.01094 |
| Opus 5.5 | $0.00042 | $0.00438 |
| Sonnet 5.5 | $0.00021 | $0.00219 |
| Haiku 4.5 | $0.00010 | $0.00109 |
Grade A, and why
sound-effects 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sound Effects
Announce at start: "I'm using the humane:sound-effects skill to make a small, coherent sound palette for this interface."
Sound is feedback, not wallpaper. Generate a short cue only when it acknowledges a change that the interface needs to make felt: a panel catching after a drag, a confirmed action, a changed mode, or a boundary reached. It is never added merely because something moves.
Before generating
- Name the moment and the change it confirms. If the interface already makes it obvious, do not add a sound.
- Read the project's token set or
DESIGN.mdwhen it exists. It supplies the material vocabulary; do not invent a second brand in audio. - Ask whether sound is opt-in, and identify motion-reduction and system sound settings. Effects must never autoplay, convey the only meaning, or prevent a task from being completed silently.
Generate a palette, not isolated noises
Start with three to five roles. Keep each effect short and quieter than a notification.
| Moment | Duration | Prompt shape |
|---|---|---|
| Press / select | 0.50 s | dry tactile click, no voice, no melody |
| Panel drag | 0.50–0.60 s | restrained low-friction mechanical glide, soft analogue texture |
| Snap / settle | 0.50 s | soft magnetic catch, rounded transient, short decay |
| Boundary | 0.50 s | muted non-alarming low pulse |
| Completion | 0.50–0.80 s | small upward confirmation tone, restrained and non-game-like |
For Humane, begin with precise, editorial, retro-futurist, tactile, quiet and exclude voice, melody, fanfare, harsh alarms, and bright game UI. Generate alternatives, then choose the family by listening side by side.
Provider adapters
ElevenLabs is the first adapter, not the architecture. The generator takes a
--provider name and loads scripts/providers/<name>.py; every adapter shares
the same prompt, duration, loop, output, and receipt contract. Read
references/provider-adapters.md before adding one. This is where another
hosted provider or local sound model can be integrated later without changing
the skill's UI rules, prompt palette, generated files, or review handoff.
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.
- 1mo ago First seen · 82 lines · 104 tokens per session scan A a02df503cd0f
sound-effects is a skill published in the GitHub repository glebis/humane-agentic-design (36 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 1,094 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…