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.
git clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/design)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/design"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/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/commands/ngocsangyem/meowkit/design"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/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.00000 | $0.00370 |
| Opus 5.5 | $0.00000 | $0.00148 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 1mo 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
/design — System Design Consultation
Usage
/design [system or feature]
Behavior
System design consultation. Output is design documentation only — does NOT generate implementation code.
Execution Steps
-
Identify components and boundaries. Analyze the system or feature to determine:
- What are the major components/services?
- Where are the boundaries between them?
- What are the responsibilities of each component?
-
Draw data flow. Produce an ASCII diagram showing:
- How data flows between components
- Entry points (API, UI, events)
- Storage layers (databases, caches, queues)
- External service integrations
[Client] → [API Gateway] → [Auth Service] → [User Service] → [PostgreSQL] → [Notification Service] → [Email Provider] -
Identify integration points. For each boundary crossing:
- What protocol is used? (HTTP, gRPC, events, direct call)
- What data format? (JSON, protobuf, etc.)
- Sync or async?
- What happens if this integration fails?
-
Flag scalability concerns. Identify potential bottlenecks:
- Single points of failure
- Components that won't scale horizontally
- Data hotspots
- Missing caching layers
- Unbounded growth patterns
-
Propose design with alternatives. Present:
- Recommended design with rationale
- At least one alternative approach
- Trade-offs between options (complexity, cost, performance, maintainability)
- Recommendation with justification
Output
Design documentation including: component diagram (ASCII), data flow, integration points, scalability analysis, and design alternatives. No implementation code is generated.
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.
- 1mo ago First seen · 53 lines · 0 tokens per session scan A 868dfc2bcfbc
design is a command published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 tokens. 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
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
review
Submit a story for verification (In Progress → In Review, no PR yet).
standup
Alias of /board — the async sprint snapshot.
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.