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 commands/terrene-foundation/metis/designgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/commands/terrene-foundation/metis/design)<a href="https://agentmods.dev/commands/terrene-foundation/metis/design"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/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.00000 | $0.00762 |
| Opus 5 | $0.00000 | $0.00381 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
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 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.
This is a copy
97% identical to design — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design - UI/UX Design Principles Quick Reference
Purpose
Load the UI/UX Design Principles skill for framework-agnostic design patterns, layout principles, and enterprise UX guidelines.
CRITICAL: This skill should be invoked PROACTIVELY for ALL frontend work, regardless of framework (React, Flutter, etc.).
Quick Reference
| Command | Action |
|---|---|
/design |
Load comprehensive design principles |
/design layout |
Show layout and information architecture patterns |
/design hierarchy |
Show visual hierarchy principles |
/design components |
Show component design guidelines |
/design responsive |
Show responsive design patterns |
What You Get
- Top-Down Design Methodology (layout → features → components → details)
- Layout & Information Architecture (70/30 rule, grid systems)
- Visual Hierarchy Principles (F-pattern, Z-pattern, inverted pyramid)
- Enterprise UX Patterns (action hierarchy, search & filter, bulk actions)
- Component Design Guidelines (cards, buttons, empty states, loading states)
- Responsive Design Patterns (breakpoints, layout changes)
- Accessibility Standards (WCAG 2.1 AA compliance)
- Design System Principles (tokens, naming conventions)
- Common Pitfalls & Solutions
Quick Principles
Top-Down Design Order (ALWAYS Follow)
LEVEL 1: FRAME/LAYOUT (Highest Priority)
→ Space division, visual hierarchy, information architecture
LEVEL 2: FEATURE COMMUNICATION
→ Discoverability, action hierarchy, navigation
LEVEL 3: COMPONENT EFFECTIVENESS
→ Widget appropriateness, interaction patterns, feedback
LEVEL 4: VISUAL DETAILS (Lowest Priority)
→ Colors, shadows, animations, typography refinements
The 70/30 Rule
- 70% of space = primary content (what user came to see/do)
- 30% of space = secondary UI (navigation, filters, chrome)
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 · 107 lines · 0 tokens per session scan A 67c58e4c2eb6
design is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 762 tokens. A static security scan graded it A with 0 findings. It is 97% identical to design, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.