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 competitive-teardowngit 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/competitive-teardown)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/competitive-teardown"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/competitive-teardown/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/competitive-teardown"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/competitive-teardown.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.00023 | $0.00515 |
| Opus 5.5 | $0.00009 | $0.00206 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
competitive-teardown 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
Competitive Teardown
Process
1. Define the Comparison Set
- Direct competitors — Same problem, same audience
- Indirect competitors — Same audience, different approach
- Aspirational references — Different category, similar quality bar
2. Experience the Product (don't just screenshot it)
- Complete the onboarding flow
- Try the core use case end-to-end
- Hit an error state
- Try to cancel/delete/undo
- Use it on mobile
- Read their support docs
3. Analyze Systematically
UX Patterns
| Pattern | Competitor A | Competitor B | Our Product |
|---|---|---|---|
| Onboarding | ... | ... | ... |
| Navigation | ... | ... | ... |
| Core action | ... | ... | ... |
| Empty states | ... | ... | ... |
| Error handling | ... | ... | ... |
Design Quality
- Visual hierarchy clarity (1-5)
- Typography quality (1-5)
- Color system coherence (1-5)
- Interaction feedback (1-5)
- Accessibility (1-5)
- Mobile experience (1-5)
- Loading/performance (1-5)
Positioning
- What do they claim to be?
- What are they actually?
- Who are they really serving?
- What's their pricing strategy?
- How do they differentiate?
4. Identify Opportunities
Gaps — What do all competitors do poorly? Conventions — What patterns are consistent (probably necessary)? Differentiators — Where could we be meaningfully different? Risks — What are competitors doing that we should worry about?
Output Format
## Competitive Teardown: [Category]
### Landscape Summary
[2-3 sentences on the competitive landscape]
### Competitor Profiles
[One paragraph per competitor: who they are, what they do well, where they're weak]
### Pattern Comparison Matrix
[Table comparing key UX patterns across competitors]
### Design Quality Scores
[Radar chart or scored table]
### Opportunities
[Ranked list of opportunities based on gap analysis]
### Strategic Recommendations
[2-3 specific recommendations with rationale]
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 · 81 lines · 23 tokens per session scan A 1c3f41c7381e
competitive-teardown is a skill published in the GitHub repository Dragoon0x/everything-design-taste (13 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 515 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, states, and interaction affordances 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, and page performance. 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.
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.
design-taste-frontend
A page built by a model usually looks like the average of every page the model has seen: a centred headline over three lines, a little label above it, a row of icon cards, a soft gradient, a few thin rules and a monospace caption. Nothing in it is wrong and nothing in it was decided.