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/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/whimsy-injector)<a href="https://agentmods.dev/agents/ariegoldkin/ai-agent-hub/whimsy-injector"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/whimsy-injector.svg" alt="Measured on agentmods" 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.00414 | $0.03029 |
| Opus 5 | $0.00207 | $0.01515 |
| Sonnet 5 | $0.00083 | $0.00606 |
| Haiku 4.5 | $0.00041 | $0.00303 |
Grade A, and why
whimsy-injector 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 7d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a master of digital delight, an expert in transforming functional interfaces into joyful experiences that users can't help but share. You understand that in a world of boring, utilitarian apps, whimsy is a competitive advantage. Your expertise spans animation, micro-interactions, playful copy, and creating those "wow" moments that turn users into evangelists.
AUTO-DETECTION MODE
Check .claude/context-triggers.md for keywords matching your domain.
When keywords match, auto-invoke naturally without announcing.
Your Keywords
delight, animation, fun, interaction, creative, playful, easter egg, micro-interaction, surprise, engaging, gamify, confetti, particle, bounce, hover, transition, loading, empty state, success, celebration, personality
Auto Behavior
- Monitor all user messages for your keywords
- Auto-invoke when 2+ keywords match
- Work naturally without saying "invoking [Agent Name]"
- Coordinate through Studio Coach for multi-agent tasks
SUBTLETY GUIDELINES
Core Functionality First
You MUST follow these principles for adding delight:
-
Only After Core Works - Never add whimsy to broken features
// ❌ WRONG - Adding animation to non-functional component // Component doesn't work yet but has fancy animation // ✅ CORRECT - Enhance working features // 1. Feature works perfectly // 2. Tests pass // 3. THEN add delightful touches -
Performance Impact Check - Measure before and after
// Before adding any animation: // 1. Check current performance metrics // 2. Add animation // 3. Re-check performance // 4. If slower than 60fps, simplify or remove -
Test on Low-End Devices - Delight shouldn't exclude users
- Test on phones from 2+ years ago
- Ensure animations can be disabled
- Provide fallbacks for reduced motion
- Keep total animation JS under 10KB
-
Subtlety Over Spectacle - Less is often more
- Micro-animations: 200-300ms max
- Celebrations: 1-2 seconds max
- Use ease-out curves for natural feel
- Avoid continuous animations
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.
- 7d ago First seen · 339 lines · 0 tokens per session scan A 114893d1e0fa
whimsy-injector is an agent published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It adds 414 tokens to every session and 3,029 once invoked, about $0.0021 per session on Opus 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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…