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 skilld-dev/skilld --skill skilld-tui-designgit clone --depth 1 https://github.com/skilld-dev/skilldWrote 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/skilld-dev/skilld/skilld-tui-design)<a href="https://agentmods.dev/skills/skilld-dev/skilld/skilld-tui-design"><img src="https://agentmods.dev/badge/skills/skilld-dev/skilld/skilld-tui-design/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/skilld-dev/skilld/skilld-tui-design"><img src="https://agentmods.dev/badge/skills/skilld-dev/skilld/skilld-tui-design.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.00047 | $0.01170 |
| Opus 5.5 | $0.00019 | $0.00468 |
| Sonnet 5.5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
skilld-tui-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design skilld CLI interactions
Build the user's whole command journey, including failure, cancellation, and the return to their shell. Read source decisions for the two reviewed Skills and their exact revisions.
Establish the contract
Read the project's GLOSSARY.md, COPY.md, and VISION.md when present.
Keep canonical nouns and strings. Use short sentences with one idea each.
Inspect the command parser, output renderer, and terminal lifecycle before changing behavior.
Classify each affected surface as static output, a picker, a prompt, or a full-screen view.
Include command help, parser errors, startup notices, and progress indicators in the inventory.
List its starting state, successful outcome, expected failures, and cancellation behavior.
Keep the existing JSON envelope, streams, and exit codes unless the task changes that contract.
Use the existing shared renderer and semantic palette.
Avoid adding a second framework or per-screen theme.
Start with crates/skilld-ui, crates/skilld-command/src/output.rs, and crates/skilld-native/src.
Inspect command help and routing in crates/skilld-command/src/lib.rs.
Put the decision first
Static output starts with the requested result or the failed action. Group repeated records consistently. Place supporting metadata below each record. Use spacing and headings before adding boxes. Keep commands copyable. Preserve whitespace inside quoted arguments. Wrap prose and paths by terminal cells. Preserve the original value in machine output. Give empty results a useful next action based on available commands.
Pickers show the question, query, matching count, selected item, and valid keys. Full-screen views keep scope and current state visible. For large inventories, start with recommendations and counts. Open projects or folders before listing individual Skills. Use words for findings. Label identical copies as duplicates and show their paths; separate symlinks from directory copies. State when a filter changes only the view. An action review must still list every affected target. Spend rows on the user's decision. Do not reserve space for decorative panels. If a pane cannot show complete content, provide reachable scrolling or a detail view. At smaller sizes, simplify the layout before hiding required information. If the screen is unusable, block hidden actions and show the required size.
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.
- 5d ago Changed · +1 lines 9bcf00153d8a
- 7d ago First seen · 101 lines · 47 tokens per session scan A bb052c5f31c9
skilld-tui-design is a skill published in the GitHub repository skilld-dev/skilld (326 stars, last pushed 5d ago), licensed MIT. It adds 47 tokens to every session and 1,170 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
web-ui
Review UI changes for responsive layout, empty states, and keyboard flow.
openai-frontend-design
Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful…
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
ultralytics-branding
This skill should be used when creating Ultralytics-branded content of any kind, including PDF, PPTX, Canva, or Google Slides presentations, DOCX documents, marketing or newsletter HTML emails, social media post copy or visuals, website or landing page designs, and dataset or model result visuals. Provides official…
lov-mobile-infographic
A mobile infographic maker that turns existing conclusions, research, or conversation content into a tall, phone-readable card. It delivers editable HTML and a PNG image.
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…