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 makifbaysal/tasktrooper --skill design-variantsgit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/design-variants)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/design-variants"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/design-variants/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/makifbaysal/tasktrooper/design-variants"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/design-variants.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.00046 | $0.01166 |
| Opus 5.5 | $0.00018 | $0.00466 |
| Sonnet 5.5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
design-variants 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Variants
Overview
Variants exist so the human can choose a direction with the alternatives in front of them — not to show effort. Two variants that differ only in colour make the human do the designer's job; five variants for a field change waste the review.
Core principle: Variants differ in structure, share the design system, are each complete in their own document, and arrive with a recommendation.
How many
Rule variant-count decides: the number the human names (description, comment or task chat), exactly; otherwise two for a new screen or flow and one for a small change to an existing screen. A design system task has none.
What makes them different
Pick the one or two axes that matter for THIS screen's main task, and vary those:
| Axis | Variant A | Variant B |
|---|---|---|
| Hierarchy — what comes first | the summary (totals, what needs attention) | the list itself |
| Layout | single column | master–detail / split view |
| Disclosure | one long page | tabs, or a stepper |
| Density | comfortable rows with secondary lines | a compact table |
| Interaction model | edit inline | edit in a dialog, or on its own page |
Never a variant axis: palette, radius, shadow, icon set, font — those belong to the design system, and all variants use the same one. Copy is the same in every variant except where the structure forces a different label.
What each variant carries
- Its own self-contained document, titled
design: <screen> · <letter>—design: Invoices — list · A,design: Invoices — list · B(screen-mockup-html). The review page lays the documents side by side; one document holding every variant cannot be compared or chosen. - A name that states the idea, in its
<h1>and#notes:Variant A — table first, notOption 1. - One line: the idea, whom it serves best, what it costs (e.g. "needs a new InvoiceSummary organism; the table is reused").
- Both widths and every state (every-state-designed). An incomplete variant cannot be approved, and an approved one with missing states becomes guesswork in the hand-off.
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.
- 4d ago First seen · 78 lines · 46 tokens per session scan A ab5d950d8231
design-variants is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,166 once invoked, about $0.0002 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-10-09.
Other skills, from other repositories
wireframe
Produce low-fidelity black-and-white UI wireframes as SVGs or viewer pages. Use when asked to wireframe, sketch a screen, draft a layout, make a low-fi mockup, or publish wireframes.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
paperclip-capsules
Generate, implement, or review Paperclip capsule visuals. Use for capsule art, agent capsules, heartbeat status capsules, identicons, capsule banks, or brand-usage validation.
presentation-template-designer
Plan reusable presentation templates from a creative brief, optional brand assets, or an existing deck. Use when Codex needs to define a slide inventory, choose an editable presentation toolchain, author or validate a template manifest, adapt a visual system for PowerPoint or Google Slides, or prepare a reviewed…
design-before-build-gate
Enforces a design/spec approval gate before production implementation. Use when UI, UX, product flows, architecture, API shape, prototypes, visual direction, or user-facing behaviour need signoff before builders write production code.
architecture-design
Use this skill to design system architecture with documented trade-offs and decisions before any implementation begins. Activates when a feature, system, or component requires non-trivial structural decisions about how components interact, what data stores to use, or how to decompose a problem.