Borrowing it
Nothing to install: this file belongs to mrgoonie/human-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mrgoonie/human-mcp/main/.claude/commands/design/describe.mdgit clone --depth 1 https://github.com/mrgoonie/human-mcpWrote 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/mrgoonie/human-mcp/describe)<a href="https://agentmods.dev/commands/mrgoonie/human-mcp/describe"><img src="https://agentmods.dev/badge/commands/mrgoonie/human-mcp/describe.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.00007 | $0.00240 |
| Opus 5 | $0.00003 | $0.00120 |
| Sonnet 5 | $0.00001 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
describe 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 7d 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.
What it actually says
Think hard to describe the design based on this screenshot/video: $ARGUMENTS
Workflow:
- Use
eyesanalyze tool to describe super details of the screenshot/video so the developer can implement it easily.- Be specific about design style, every element, elements' positions, every interaction, every animation, every transition, every color, every border, every icon, every font style, font size, font weight, every spacing, every padding, every margin, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every image, background transparency, etc.
- IMPORTANT: Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use Inter or Poppins.
- Use
ui-ux-designersubagent to create a design implementation plan of creating exactly the same result with the screenshot/video, break down the plan into TODO tasks in./plansdirectory. - Report back to user with a summary of the plan.
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.
- 7d ago First seen · 13 lines · 7 tokens per session scan A 756fe0623000
describe is a command published in the GitHub repository mrgoonie/human-mcp (294 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 240 once invoked, about $0.0000 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-30.
Other commands, from other repositories
diagram
Generate architecture diagrams using Mermaid or ASCII art for system visualization.
style
Apply styling to a component using the project's design system and styling approach.
generate-report
Generate a detailed accessibility audit report with remediation steps.
run-audit
Execute a comprehensive accessibility audit against WCAG guidelines.
check-contrast
Check color contrast ratios against WCAG accessibility requirements.
suggest-colors
Suggest alternative colors that meet WCAG contrast requirements.