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/jcarlosrodicio/opencode-agent-orchestration-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/commands/jcarlosrodicio/opencode-agent-orchestration-kit/design)<a href="https://agentmods.dev/commands/jcarlosrodicio/opencode-agent-orchestration-kit/design"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/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/jcarlosrodicio/opencode-agent-orchestration-kit/design"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/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.00021 | $0.00274 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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 the following:
$ARGUMENTS
Mandatory flow:
- Search for and read
PRODUCT.mdandDESIGN.md. - If either is missing, load
impeccableand create or propose the missing document(s). - Load
open-design. - Resolve
baseUrlfrom approved safe configuration or explicit user/lead context. - If
baseUrlis missing, stop and ask; do not guess or hardcode URLs. - Check
open_design_healthwith the resolvedbaseUrl. - Check
open_design_list_agentswith the resolvedbaseUrl. - Choose the best Open Design
skillId. - Choose the best
designSystemId. - Use
open_design_run_designwith the resolvedbaseUrlonly when generated files are explicitly requested. - Otherwise use
open_design_create_projectwith the resolvedbaseUrlfor an editable workbench project. - Return project URL, prompt, decisions, assumptions, risks, visual acceptance criteria, and developer handoff.
Never invent URLs or hardcode baseUrl; it must come from approved configuration/context.
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 · 28 lines · 21 tokens per session scan A 8971b86817b0
design is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (136 stars, last pushed 20d ago), licensed Apache-2.0. It adds 21 tokens to every session and 274 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
live-canvas
Conduct design interviews, generate UI variations, and collect live click-to-annotate feedback that streams into the session so edits land without leaving the browser. Use when the user wants rapid iterative UI refinement, not just batched feedback.
balance-check
Analyze game balance data and configurations.
consistency-check
Detect cross-document inconsistencies.
review-all-gdds
Cross-GDD consistency and game design review.
art-bible
Guided visual identity specification authoring.
design-system
Section-by-section GDD authoring.