Borrowing it
Nothing to install: this file belongs to ECD5A/OrchestrUI. 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/ECD5A/OrchestrUI/main/AGENTS.mdgit clone --depth 1 https://github.com/ECD5A/OrchestrUIWrote 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/instructions/ecd5a/orchestrui/agents-md)<a href="https://agentmods.dev/instructions/ecd5a/orchestrui/agents-md"><img src="https://agentmods.dev/badge/instructions/ecd5a/orchestrui/agents-md/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/instructions/ecd5a/orchestrui/agents-md"><img src="https://agentmods.dev/badge/instructions/ecd5a/orchestrui/agents-md.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.00418 | $0.00418 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
OrchestrUI AGENTS.md 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 2mo 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
OrchestrUI repository instructions
Mission
OrchestrUI is an agent-facing UI/UX orchestration layer for Kokonut UI, React Bits, daisyUI, Bklit UI, Anime.js, Rive, and Magic UI. It is not a vendor dump.
Source of truth
- Current official upstream docs/repos are authoritative.
- Verify package names, registry URLs, component IDs, MCP setup and licenses before changing integrations.
- Keep
catalog/*.jsonmachine-readable.
Legal guardrails
- Never vendor or redistribute the React Bits component collection from OrchestrUI.
- Never copy paid/Pro content, credentials, authenticated registry material or license keys.
- Treat Rive runtime licensing separately from
.rivasset rights. - Do not imply upstream endorsement or partnership.
Routing principles
- Inspect the host project first.
- Existing design systems win unless migration is explicit.
- Use the fewest libraries needed.
- Give each major UI role one owner.
- Bklit is the preferred chart/data-viz specialist.
- Add Anime.js only when built-in/CSS motion is insufficient.
- Use Rive only for meaningful interactive vector/state-machine graphics with known asset rights.
- Avoid accidental daisyUI/shadcn base-system conflicts.
- Accessibility, responsiveness, performance and coherence outrank novelty.
Workflow
- Read
.agents/skills/ui-library-router/SKILL.md. - Inspect the host stack and produce a short selection plan.
- Read
.agents/skills/ui-orchestrator/SKILL.md. - Retrieve current official upstream information only for selected libraries.
- Harmonize typography, spacing, radius, color, surfaces, shadows and motion.
- Implement responsive and accessible behavior.
- Run host-project checks.
- Read
.agents/skills/ui-quality-audit/SKILL.mdbefore completion.
Repository gates
npm run validatenpm test- exactly seven core libraries
- valid skill frontmatter
- no secrets, paid/Pro source or mirrored component collections
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.
- 2mo ago First seen · 44 lines · 418 tokens per session scan A 766a551e09f0
OrchestrUI AGENTS.md is an instructions file published in the GitHub repository ECD5A/OrchestrUI (1 stars, last pushed yesterday), licensed MIT. It adds 418 tokens to every session, about $0.0017 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.