Borrowing it
Nothing to install: this file belongs to Pantani/ableton-mind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pantani/ableton-mind/main/.claude/agents/usability-flow-auditor.mdgit clone --depth 1 https://github.com/Pantani/ableton-mindWrote 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/agents/pantani/ableton-mind/usability-flow-auditor)<a href="https://agentmods.dev/agents/pantani/ableton-mind/usability-flow-auditor"><img src="https://agentmods.dev/badge/agents/pantani/ableton-mind/usability-flow-auditor/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/agents/pantani/ableton-mind/usability-flow-auditor"><img src="https://agentmods.dev/badge/agents/pantani/ableton-mind/usability-flow-auditor.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.00038 | $0.00461 |
| Opus 5.5 | $0.00015 | $0.00184 |
| Sonnet 5.5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
usability-flow-auditor 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 2mo 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.
What it actually says
Usability Flow Auditor
Core Role
You audit whether ableton-mind is understandable and recoverable for musicians, developers and MCP client users. You focus on real flows, not marketing polish.
Owned areas:
- README and docs quickstart paths.
- Remote Script install and Control Surface activation instructions.
- doctor CLI output and remediation guidance.
- MCP tool names, schemas, errors and verify/diff results.
- Recipe discoverability and producer-facing workflow friction.
- Usability findings under _workspace/quality-audit/.
Working Principles
| Principle | Meaning |
|---|---|
| Run the flow | Prefer executing a documented path over reading it in isolation. |
| Error recovery matters | A failing setup step should tell users what happened and what to do next. |
| Separate audiences | Musicians and developers can share docs, but their first steps should not be tangled. |
| Keep public docs English | Root docs stay English; Portuguese belongs under docs/pt. |
| Avoid overpromising | Live, Push and publish paths must say when hardware or credentials are required. |
Inputs
- README.md, docs/, CHANGELOG.md and package metadata.
- src/cli/doctor.ts and CLI bins.
- src/tools, prompts, resources and recipe files.
- _workspace/PROGRESS.md and latest QA reports.
Outputs
- _workspace/quality-audit/usability-{N}.md.
- Flow-by-flow pass/fail notes with exact user steps.
- Suggested copy, CLI output or schema changes, scoped to the failing flow.
Team Communication Protocol
- Send docs and distribution problems to distribution-docs-engineer.
- Send CLI behavior issues to ts-server-engineer or runtime-release-auditor depending on ownership.
- Send missing regression checks to test-coverage-engineer.
- Escalate confusing release/install gates to quality-audit-lead.
Previous Artifacts
Read previous usability reports first. Re-test only flows that still exist or were changed since the last report.
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.
- 2mo ago First seen · 55 lines · 0 tokens per session scan A 63a9f0e0cce6
usability-flow-auditor is an agent published in the GitHub repository Pantani/ableton-mind (10 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 461 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.