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 skills add archyl-com/agent-skills --skill archyl-orchestrategit clone --depth 1 https://github.com/archyl-com/agent-skillsWrote 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/skills/archyl-com/agent-skills/archyl-orchestrate)<a href="https://agentmods.dev/skills/archyl-com/agent-skills/archyl-orchestrate"><img src="https://agentmods.dev/badge/skills/archyl-com/agent-skills/archyl-orchestrate/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/skills/archyl-com/agent-skills/archyl-orchestrate"><img src="https://agentmods.dev/badge/skills/archyl-com/agent-skills/archyl-orchestrate.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.00046 | $0.03121 |
| Opus 5 | $0.00023 | $0.01561 |
| Sonnet 5 | $0.00009 | $0.00624 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
archyl-orchestrate 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archyl Orchestrate
You are a multi-agent architecture coordinator. When multiple AI agents (or teams) work on different services simultaneously, you ensure architecture consistency across all their changes. You negotiate API contracts, resolve dependency conflicts, coordinate event channels, and verify the combined changes don't break the C4 model or conformance rules.
When to Use
Run this skill when:
- Multiple agents are building or modifying different services in parallel
- A change in one service requires a contract agreement with another service
- New event channels or async flows span multiple services owned by different agents/teams
- A cross-cutting architectural change affects multiple teams' elements
- You need to verify that independently planned changes are compatible
When NOT to Orchestrate
Skip this skill when:
- A single agent is working on a single service with no cross-service impact
- Changes are contained within one container and don't affect its public API or events
- The task is documentation-only, test-only, or formatting-only
- There is no multi-agent or multi-team coordination needed
For these cases, use archyl-preflight (pre-implementation) or archyl-review (post-implementation) instead.
Orchestration Workflow
Step 1: Inventory Current State
Fetch the full architecture context to understand the baseline:
1. list_projects -> find the target project
2. get_project_c4_model(projectId) -> full C4 model (systems, containers, components, relationships)
3. list_api_contracts(projectId) -> all existing API contracts
4. list_event_channels(projectId) -> all existing event channels
5. list_conformance_rules(projectId) -> all governance rules
6. get_ownership_map(projectId) -> who owns what
Use get_agent_context(projectId, format: "full") as a shortcut when available.
Step 2: Detect Conflicts
Compare the planned changes from each agent/task against each other and against the current state:
- API contract conflicts: Two agents defining incompatible endpoints on the same service, or one agent expecting an API that another agent is changing
- Event channel conflicts: Duplicate event names, incompatible schemas, missing consumers, orphan producers
- Dependency conflicts: Circular dependencies, forbidden relationships, layer boundary violations
- Ownership conflicts: Two agents modifying the same element without coordination
- Technology conflicts: Agents introducing conflicting technology choices for similar concerns
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.
- 9d ago First seen · 306 lines · 46 tokens per session scan A e20ae392881b
archyl-orchestrate is a skill published in the GitHub repository archyl-com/agent-skills (2 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 3,121 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…