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 Dragoon0x/everything-design-taste --skill event-ticketinggit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/event-ticketing)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/event-ticketing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/event-ticketing/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/dragoon0x/everything-design-taste/event-ticketing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/event-ticketing.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.00022 | $0.00285 |
| Opus 5.5 | $0.00009 | $0.00114 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
event-ticketing 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.
What it actually says
Event & Ticketing Design
Event Discovery
- Visual calendar or list view
- Filter: date, category, location, price range
- Featured/promoted events section
- Personalized recommendations
- Save/bookmark events
- Share event with friends
Event Detail Page
- Hero image or event banner
- Title, date/time, venue, organizer
- Clear pricing (ticket types and ranges)
- Seat map (if seated venue)
- Description, lineup, schedule
- Venue info with map
- "Add to Calendar" button
- Social proof (X attending, friends going)
Ticket Selection
- Ticket types: name, price, description, availability
- Quantity selector with per-type limits
- Seat map: interactive, color-coded by price/section
- Show view from seat (if available)
- Accessibility seating options visible
- Timer for reservation hold (10-15 minutes)
Checkout
- Order summary with ticket details
- Attendee info collection (per ticket if required)
- Payment processing
- Confirmation with QR code / barcode
- Email confirmation with calendar attachment
- Digital wallet pass option (Apple Wallet, Google Wallet)
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 · 42 lines · 22 tokens per session scan A f4722f155316
event-ticketing is a skill published in the GitHub repository Dragoon0x/everything-design-taste (13 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 285 once invoked, about $0.0001 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-03.
Other skills, from other repositories
antislop
Anti Slop: Rules for AI Coding Agents. The core filter. Load always to stop generic AI slop.
antislop-human
Human and accessibility skill for antislop. Contrast, keyboard, focus, and states for real people. Includes the contrast checker.
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
role-ui-ux-designer
Use when orchestrating UI/UX design systems, anti-AI-slop frontend styling, tactile micro-interactions, responsive design tokens, accessibility standards, and high-fidelity interface engineering.
forms-inputs-checkout
Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow.
taste
Anti-slop frontend engineering directive and design taste system. Enforces brief inference, dynamic design dials, absolute prohibition of AI visual tells, and 100% full-output completion.