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/zeeshanhanif/agentic-sdlc-kit/ui-designnpx skills add zeeshanhanif/agentic-sdlc-kit --skill ui-designgit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/ui-design)<a href="https://agentmods.dev/skills/zeeshanhanif/agentic-sdlc-kit/ui-design"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/ui-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.00209 | $0.02720 |
| Opus 5 | $0.00105 | $0.01360 |
| Sonnet 5 | $0.00042 | $0.00544 |
| Haiku 4.5 | $0.00021 | $0.00272 |
Grade A, and why
ui-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 5d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design
The presentation half of the feature's low-level design — detailed-design's conceptual sibling, but sequential in the loop: in per-feature mode this skill consumes the feature's technical-design.md (screens bind to its contracts — a screen displays what an endpoint returns), which is why detailed-design runs first. Only anchor mode, which precedes any feature, has no such dependency. It answers, per screen: what does it look like, what does it compose from, what states does it cover, where does its design authority live. Its defining characteristic is that it's an adapter: how screens get designed varies by project (an existing design file, a generation tool, straight to code), so this skill routes across strategies while emitting one uniform output contract — the design manifest — that everything downstream reads, whatever produced each screen. All design-tool variance is absorbed here; no downstream skill ever learns what a Figma node is.
Three principles govern it:
- Strategy is resolved per screen, not per project. A project with a partial design file is "register" for the screens that exist and the project's fallback policy for the rest. The manifest lookup by SCR ID is always the first move.
- Screens conform to the design system or escalate — never fork it.
docs/design.md+tokens.jsonare the authority. A fetched or generated screen introducing an off-system color, component, or pattern is either corrected to the system, or the system is amended through ux-foundations' amendment path (the presentation analog of detailed-design's schema escalation). Local work never silently mutates upstream authority. - The manifest is the only registry. With per-screen routing, no design
tool ever holds the complete picture — only
docs/design-manifest.jsondoes. This skill is its single writer.
Inputs
Defaults below; user paths win; source-gated citation throughout (SCR/FEAT/ FR/UC/NFR IDs only from documents that exist; never fabricate).
What ships with it
5 files 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.
- 5d ago First seen · 222 lines · 209 tokens per session scan A 38f59b4cc74a
ui-design is a skill published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 10d ago), licensed Apache-2.0. It adds 209 tokens to every session and 2,720 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…