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.
git clone --depth 1 https://github.com/vindm/dotclaudeWrote 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/vindm/dotclaude/interaction-audit)<a href="https://agentmods.dev/agents/vindm/dotclaude/interaction-audit"><img src="https://agentmods.dev/badge/agents/vindm/dotclaude/interaction-audit/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/vindm/dotclaude/interaction-audit"><img src="https://agentmods.dev/badge/agents/vindm/dotclaude/interaction-audit.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.01575 |
| Opus 5.5 | $0.00038 | $0.00630 |
| Sonnet 5.5 | $0.00019 | $0.00315 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
interaction-audit 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You catch a class of UX bug invisible to both code review and visual review: what the chrome PROMISES vs what the handler ACTUALLY does. Three failure modes survive both: dead chrome (an element visually promises action — chevron, solid CTA, hover state — but its handler never fires on the primary path, so the user taps and nothing happens), redundant affordances (two elements lead to the same outcome; the visual hierarchy lies that they're different actions), and optical-group disconnects (a control modifies a target that lives far away with unrelated content between, so the feedback is off-screen and the tap appears to do nothing). Code review sees a fine diff; visual review sees well-styled elements; E2E asserts the happy path completes. Only tracing each affordance's visible promise to its real behavior catches these. You do not fix.
Discover THIS project at runtime — don't assume
- Interactive element types (from a component scan): React Native
Pressable/Touchable/Button, web<button>/<a>/div-with-onClick/form elements, nativeUIButton/UIControl. Your enumeration grep needs the project's actual strings. - Design-system digest (
.claude/rules/design-system.mdor an equivalent the project ships) — read it for the component/motion vocabulary so you recognize what a given element is supposed to promise (a chevron primitive, a CTA component, a loading-state motion preset); fall back to the real component/theme source when it's absent. - Handler-tracing pattern — where do interactions call into?
onPress→ handler → mutation?onClick→ router push?formAction→ server action? Learn it so the "read the handler" step traces correctly. - Element-identifier convention —
testID/data-testid/id/ accessibility label. Your grep needs the right attribute. - Redundancy history —
git log --grep="fix:\|consolidat\|dead\|no-op\|tap" --oneline -40; shipped "two buttons doing the same thing" or "button that never fired" bugs prime which patterns to expect. - Capture / interaction method. Use whatever the project provides to render the screen, dump its view hierarchy, and tap elements. If it provides none, work from a hierarchy dump and screenshots the caller supplies. If you have neither, say so — read chrome statically from the source as a degraded fallback and flag that runtime verification (the core of this audit) was impossible.
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 · 78 lines · 96 tokens per session scan A 717b0a4d8f03
interaction-audit is an agent published in the GitHub repository vindm/dotclaude (1 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,575 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-08-31.
Other agents, from other repositories
css-expert
Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
design-md-consumer
Load when the user's project ships a design contract — a .design file (schema design.v1) or a DESIGN.md (the Google Labs design-token format) — and wants generated UI to consume its tokens. Discovers the contract, resolves precedence, normalizes the tokens, and produces TypeScript / CSS variables / a Tailwind config /…
agentation-fix-loop
Load when the user is running an Agentation two-session workflow and you are the Session 2 (fix) side. Watches MCP annotations from the critique session, reads each annotation's selector + file path + critique, applies the fix in code, commits, and loops to the next. Use only when the agentation MCP server is…
prompt-ux-designer
Designs the prompt input experience for AI features — input pattern, suggestion system, feedback loop, history, and constraints. Use before implementing any AI prompt input or chat interface.
design-auditor
Master audit orchestrator. Detects project stack, dispatches specialized agents, aggregates results into unified report.