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 DNYoussef/context-cascade --skill coordinationgit clone --depth 1 https://github.com/DNYoussef/context-cascadeWrote 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/dnyoussef/context-cascade/coordination)<a href="https://agentmods.dev/skills/dnyoussef/context-cascade/coordination"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/coordination/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/dnyoussef/context-cascade/coordination"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/coordination.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.01901 |
| Opus 5.5 | $0.00000 | $0.00760 |
| Sonnet 5.5 | $0.00000 | $0.00380 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
coordination 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/============================================================================/ /* COORDINATION SKILL :: VERILINGUA x VERIX EDITION / /============================================================================*/
name: coordination version: 2.0.0 description: | [assert|neutral] Advanced multi-agent coordination patterns including mesh, hierarchical, and adaptive topologies with state synchronization, consensus mechanisms, and distributed task execution. Use when orchestratin [ground:given] [conf:0.95] [state:confirmed] category: orchestration tags:
- coordination
- multi-agent
- orchestration
- topology
- consensus author: ruv cognitive_frame: primary: aspectual goal_analysis: first_order: "Execute coordination workflow" second_order: "Ensure quality and consistency" third_order: "Enable systematic orchestration processes"
/----------------------------------------------------------------------------/ /* S0 META-IDENTITY / /----------------------------------------------------------------------------*/
[define|neutral] SKILL := { name: "coordination", category: "orchestration", version: "2.0.0", layer: L1 } [ground:given] [conf:1.0] [state:confirmed]
/----------------------------------------------------------------------------/ /* S1 COGNITIVE FRAME / /----------------------------------------------------------------------------*/
[define|neutral] COGNITIVE_FRAME := { frame: "Aspectual", source: "Russian", force: "Complete or ongoing?" } [ground:cognitive-science] [conf:0.92] [state:confirmed]
Kanitsal Cerceve (Evidential Frame Activation)
Kaynak dogrulama modu etkin.
/----------------------------------------------------------------------------/ /* S2 TRIGGER CONDITIONS / /----------------------------------------------------------------------------*/
[define|neutral] TRIGGER_POSITIVE := { keywords: ["coordination", "orchestration", "workflow"], context: "user needs coordination capability" } [ground:given] [conf:1.0] [state:confirmed]
/----------------------------------------------------------------------------/ /* S3 CORE CONTENT / /----------------------------------------------------------------------------*/
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/example-1-hierarchical-swarm.md 17 KB
- examples/example-2-mesh-topology.md 20 KB
- examples/example-3-adaptive-scaling.md 23 KB
- manifest.json 1.0 KB
- readme.md 9.5 KB
- resources/scripts/init-hierarchical-topology.js 4.0 KB runs code
- resources/scripts/init-mesh-topology.js 2.8 KB runs code
- resources/scripts/orchestrate-distributed-task.js 3.3 KB runs code
- resources/scripts/spawn-coordinated-agents.js 3.4 KB runs code
- resources/scripts/topology-selector.js 5.7 KB runs code
- resources/templates/adaptive-topology.yaml 4.7 KB
- resources/templates/agent-roles.yaml 5.4 KB
- resources/templates/hierarchical-topology.yaml 4.2 KB
- resources/templates/mesh-topology.yaml 2.9 KB
- tests/test-consensus-mechanisms.js 14 KB runs code
- tests/test-hierarchical-topology.js 9.6 KB runs code
- tests/test-mesh-topology.js 8.0 KB runs code
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 · 197 lines · 0 tokens per session scan A fe2e87f14450
coordination is a skill published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,901 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-09-03.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…