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 when-orchestrating-swarm-use-swarm-orchestrationgit 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/when-orchestrating-swarm-use-swarm-orchestration)<a href="https://agentmods.dev/skills/dnyoussef/context-cascade/when-orchestrating-swarm-use-swarm-orchestration"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/when-orchestrating-swarm-use-swarm-orchestration/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/when-orchestrating-swarm-use-swarm-orchestration"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/when-orchestrating-swarm-use-swarm-orchestration.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.02003 |
| Opus 5.5 | $0.00000 | $0.00801 |
| Sonnet 5.5 | $0.00000 | $0.00401 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
when-orchestrating-swarm-use-swarm-orchestration 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/============================================================================/ /* WHEN-ORCHESTRATING-SWARM-USE-SWARM-ORCHESTRATION SKILL :: VERILINGUA x VERIX EDITION / /============================================================================*/
name: when-orchestrating-swarm-use-swarm-orchestration version: 1.0.0 description: | [assert|neutral] Complex multi-agent swarm orchestration with task decomposition, distributed execution, and result synthesis [ground:given] [conf:0.95] [state:confirmed] category: workflow tags:
- swarm
- orchestration
- coordination
- task-decomposition
- result-synthesis author: ruv cognitive_frame: primary: evidential goal_analysis: first_order: "Execute when-orchestrating-swarm-use-swarm-orchestration workflow" second_order: "Ensure quality and consistency" third_order: "Enable systematic workflow processes"
/----------------------------------------------------------------------------/ /* S0 META-IDENTITY / /----------------------------------------------------------------------------*/
[define|neutral] SKILL := { name: "when-orchestrating-swarm-use-swarm-orchestration", category: "workflow", version: "1.0.0", layer: L1 } [ground:given] [conf:1.0] [state:confirmed]
/----------------------------------------------------------------------------/ /* S1 COGNITIVE FRAME / /----------------------------------------------------------------------------*/
[define|neutral] COGNITIVE_FRAME := { frame: "Evidential", source: "Turkish", force: "How do you know?" } [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: ["when-orchestrating-swarm-use-swarm-orchestration", "workflow", "workflow"], context: "user needs when-orchestrating-swarm-use-swarm-orchestration capability" } [ground:given] [conf:1.0] [state:confirmed]
/----------------------------------------------------------------------------/ /* S3 CORE CONTENT / /----------------------------------------------------------------------------*/
What ships with it
4 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.
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 · 211 lines · 0 tokens per session scan A 3ff5da50a6fd
when-orchestrating-swarm-use-swarm-orchestration 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 2,003 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.