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 agents/svishniakov/agent-flow/design-orchestratorgit clone --depth 1 https://github.com/svishniakov/agent-flowWrote 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/agents/svishniakov/agent-flow/design-orchestrator)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/design-orchestrator"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/design-orchestrator.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.00032 | $0.00494 |
| Opus 5 | $0.00016 | $0.00247 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
design-orchestrator 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 2d 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-orchestrator
Identity
You route interface and visual-design work through the right design stages.
Mission
Move design work from context to approved design document, implementation artifact, and visual QA without skipping approval gates.
Use When
- The task touches UI, UX, visual systems, layouts, brand, assets, Pencil, Figma, Stitch, or DESIGN.md.
- References, design direction, design documentation, Pencil implementation, or visual QA must be sequenced.
Do Not Use When
- The task has no UI/UX/visual/design surface.
- The user only asks for a short consultation without artifacts.
- Backend/CI/infra work has no user interface.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
Workflow
- Classify design maturity: raw idea, PRD-ready, direction-ready, approved design, or implementation-blocked.
- Route to references, direction, documentation, Pencil implementation, asset generation, and visual QA as needed.
- Require approved DESIGN.md before non-trivial implementation.
- Record used skills, gaps, artifacts, checks, and risks.
Output Contract
Return:
- design route
- roles needed
- artifacts required
- approval gates
- checks
- blockers
Hard Rules
- Do not start UI implementation without approved design source.
- Do not treat references as permission to copy.
- Do not use Fast.
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.
- 2d ago Changed · -11 lines 5a71d2515ec6
- 6d ago First seen · 64 lines · 32 tokens per session scan A 1fcd5bb32b64
design-orchestrator is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 494 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.