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 case-study-writinggit 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/case-study-writing)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/case-study-writing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/case-study-writing/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/case-study-writing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/case-study-writing.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.00027 | $0.00538 |
| Opus 5.5 | $0.00011 | $0.00215 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
case-study-writing 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Study Writing
Structure
The Honest Arc
- Context — Company, timeline, your role, team size. No fluff. Just facts.
- Problem — What was broken, missing, or failing. Be specific with metrics if you have them.
- Constraints — What made this hard. Budget, timeline, technical limits, organizational politics. Constraints make the story real.
- Process — What you actually did. Not a waterfall diagram. The real, messy process including dead ends.
- Key decisions — The 2-3 decisions that mattered most. What were the options? Why did you choose what you chose?
- What failed — What didn't work. What you tried and abandoned. This is where credibility lives.
- Outcome — Measurable results. Revenue, conversion, engagement, adoption, time saved. Numbers beat adjectives.
- Reflection — What you'd do differently. What you learned.
Common Mistakes
- Starting with "I was tasked with..." (passive, boring)
- Showing only the happy path (nobody believes it)
- Screenshot galleries with no explanation
- Process diagrams that describe methodology, not actual work
- Focusing on deliverables instead of decisions
- No metrics (words like "improved" and "enhanced" mean nothing alone)
- Writing for other designers instead of the intended audience
Writing Quality
Lead with the Outcome
Don't make people read 2000 words to find out what happened. State the result upfront, then explain how you got there.
Bad opening: "In Q3 2024, the team identified an opportunity to improve the onboarding experience..."
Good opening: "We cut onboarding drop-off by 34% in six weeks. Here's the decision that made the difference."
Show Your Thinking
Screenshots of final designs are the least interesting part. Show:
- The whiteboard sketch that unlocked the solution
- The comparison of 3 approaches you considered
- The data that changed your mind
- The prototype that users rejected (and why)
Write for Your Audience
- For hiring managers: emphasize process, collaboration, impact
- For founders: emphasize speed, business outcomes, constraints handled
- For peers: emphasize craft decisions, technical tradeoffs, methodology
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 · 50 lines · 27 tokens per session scan A f214a71000a0
case-study-writing is a skill published in the GitHub repository Dragoon0x/everything-design-taste (13 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 538 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-code
Code comment hygiene for AI coding agents: remove generic AI-slop comments, keep the valuable ones, never touch the code.
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
antislop-copywriting
Copy and text skill for antislop. Use when writing or editing prose: headlines, tone, CTAs, and anti-AI-writing patterns. Load with the core.
antislop-layoutmobile
Mobile layout skill for antislop. Use for layouts that reflow across screen sizes, phone to desktop: grids, overflow, tap targets. Load with the core.