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/taste-skills --skill taste-as-strategygit clone --depth 1 https://github.com/Dragoon0x/taste-skillsWrote 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/taste-skills/taste-as-strategy)<a href="https://agentmods.dev/skills/dragoon0x/taste-skills/taste-as-strategy"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/taste-as-strategy/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/taste-skills/taste-as-strategy"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/taste-as-strategy.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.00065 | $0.00971 |
| Opus 5.5 | $0.00026 | $0.00388 |
| Sonnet 5.5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
taste-as-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taste as Strategy
Execution is getting cheaper every month. Taste is the moat.
How to use
/taste-as-strategyApply taste-as-strategy thinking to product and business decisions in this conversation.
Constraints
The Strategic Case
- MUST recognize that AI and vibe-coding are commoditizing execution. Anyone can build an interface now. The differentiator is knowing which interface to build, what it should feel like, and what to leave out.
- MUST frame taste as a decision-making advantage, not an aesthetic one. Taste means faster, better product decisions. It means knowing what to cut. It means recognizing when something is off before users report it.
- Taste compounds. Every good decision creates context for the next good decision. Products with taste get better faster than products without it.
- NEVER position taste as "making things pretty." That's craft. Taste is judgment applied to strategy, product, experience, and communication simultaneously.
Taste as Moat
- Products with strong taste are harder to copy than products with strong features. Features can be replicated. The judgment behind which features to build, how they feel, and what's deliberately absent cannot.
- MUST evaluate: can a competitor with more resources but less taste replicate this experience? If yes, taste isn't the moat yet. If no, taste is the moat.
- Stripe's moat isn't payments infrastructure. It's the taste that makes developers feel respected. Notion's moat isn't blocks. It's the taste that makes the tool feel like a creative instrument. Linear's moat isn't issue tracking. It's the taste that makes project management feel precise.
- SHOULD identify where taste creates switching costs that features alone don't.
Taste in the AI Era
- When everyone can generate code, design, and copy, the bottleneck shifts from "can we build this" to "should we build this" and "does this feel right"
- MUST recognize that AI amplifies taste. A person with strong taste and AI tools produces extraordinary work. A person with weak taste and AI tools produces polished mediocrity at scale.
- SHOULD evaluate AI-generated output through taste filters, not just correctness filters. Does it feel right? Does it match the product's voice? Would a human with great judgment have made this choice?
- The teams that win are the ones where taste is the operating system and AI is the execution layer.
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 · 59 lines · 65 tokens per session scan A e64f965723e7
taste-as-strategy is a skill published in the GitHub repository Dragoon0x/taste-skills (7 stars, last pushed 8mo ago), licensed MIT. It adds 65 tokens to every session and 971 once invoked, about $0.0003 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 skills, from other repositories
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
work-with-creators-creator-vetting
Vets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
Accessibility Manual Audit
Teach agents to guide manual accessibility audits for keyboard, screen reader, zoom, reflow, focus, and WCAG 2.2 criteria that scanners miss.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.