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 agentmods add skills/7xmohamed/kata/designnpx skills add 7xmohamed/Kata --skill designgit clone --depth 1 https://github.com/7xmohamed/KataWrote 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/7xmohamed/kata/design)<a href="https://agentmods.dev/skills/7xmohamed/kata/design"><img src="https://agentmods.dev/badge/skills/7xmohamed/kata/design.svg" alt="Measured on agentmods" 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.00041 | $0.02816 |
| Opus 5 | $0.00020 | $0.01408 |
| Sonnet 5 | $0.00008 | $0.00563 |
| Haiku 4.5 | $0.00004 | $0.00282 |
Grade A, and why
design 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 6d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design: Production-Grade Frontend UI
Prefix your first line with ⚔️ inline, not as its own paragraph.
If it could have been generated by a default prompt, it is not good enough.
Screenshot Iteration Mode
Activate when the user sends a screenshot or image alongside a complaint ("这里很丑", "这个不对", "fix this", "looks wrong"). The existing product is the direction. Skip the five-question direction lock.
Flow:
- Read the screenshot. State the problem in one sentence: what specifically looks wrong (spacing, contrast, alignment, typeface, color).
- Wait for the user to confirm the diagnosis before touching code.
- If the diagnosis is a known UX problem (split-view sync, infinite scroll, virtualised list, sticky header), spend one round surveying how 2-3 mature products in the same category solve it before writing code. Cite what each does. Skip only if the fix is purely cosmetic (color, spacing, copy).
- Find the responsible code: grep for the component name or class, read the actual file. Do not rely on memory or assumptions about file location.
- Apply the minimal fix. One component, one issue.
- Ask the user to verify in the browser. Do not hand off without this step.
Boundary: if the fix requires changing 3 or more components, or if it reveals a direction problem rather than a specific bug, pause and run the full direction lock before continuing.
Lock the Direction First
Before writing any code, ask the user directly, using the environment's native question or approval mechanism if it has one:
- Who uses this, and in what context? Analyst dashboard differs from landing page or onboarding flow. See "App shell exception" below if the answer is a sidebar + main workspace layout.
- What is the aesthetic direction? Name it precisely: dense editorial, raw terminal, ink-on-paper, brutalist grid, warm analog. "Clean and modern" is not a direction. If the user names a reference site or product ("feels like Linear / Gemini.ai / Vercel"), do not accept it as a direction -- extract 3 concrete properties from it: button radius philosophy, surface depth treatment (shadow vs background step vs border), and accent color family. Name those instead.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 154 lines · 41 tokens per session scan A 618335cc233d
design is a skill published in the GitHub repository 7xmohamed/Kata (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,816 once invoked, about $0.0002 per session on Opus 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
antigravity-helper
Use when the user wants to invoke Antigravity CLI for a code review of uncommitted changes or a branch diff, an adversarial design-challenge review, or to delegate a coding task to Antigravity for a second opinion or large-context analysis. Wraps the antigravity-cli-plugin-cc companion script.
taskwing-plan
Use when you need to clarify a goal and build an approved execution plan.
taskwing-next
Use when you are ready to start the next approved TaskWing task with full context.
taskwing-done
Use when implementation is verified and you are ready to complete the current task.
taskwing-context
Use when you need project knowledge for architectural context. Returns a compact summary by default.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.