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 cyanheads/openfoodfacts-mcp-server --skill orchestrationsgit clone --depth 1 https://github.com/cyanheads/openfoodfacts-mcp-serverWrote 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/cyanheads/openfoodfacts-mcp-server/orchestrations)<a href="https://agentmods.dev/skills/cyanheads/openfoodfacts-mcp-server/orchestrations"><img src="https://agentmods.dev/badge/skills/cyanheads/openfoodfacts-mcp-server/orchestrations/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/cyanheads/openfoodfacts-mcp-server/orchestrations"><img src="https://agentmods.dev/badge/skills/cyanheads/openfoodfacts-mcp-server/orchestrations.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.00159 | $0.05680 |
| Opus 5.5 | $0.00064 | $0.02272 |
| Sonnet 5.5 | $0.00032 | $0.01136 |
| Haiku 4.5 | $0.00016 | $0.00568 |
Grade A, and why
orchestrations 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 4d 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.
This is a copy
100% identical to orchestrations — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Multi-phase work that chains several foundational skills against one or more MCP server projects. Typical triggers:
- "Build N new servers" / "scaffold and ship X, Y, Z" →
workflows/greenfield-build.md - "Update and release these servers" / "run maintenance and ship" →
workflows/maintenance-release.md - "QA / field-test / find-and-fix bugs in these servers" →
workflows/field-test-fix.md - "Fix these issues and ship" / handoff document with findings to act on →
workflows/fix-wrapup-release.md
Single-skill work — running just maintenance, just git-wrapup, just release-and-publish — invokes the foundational skill directly. Use this orchestrations skill when at least two phases need to chain.
Mental Model — Three Tiers
| Tier | Layer | Examples | Who reads it |
|---|---|---|---|
| 1 | Foundational task skills | git-wrapup, release-and-publish, maintenance, field-test, setup, design-mcp-server, polish-docs-meta, code-simplifier, add-tool, add-resource, add-service, add-test, etc. |
Orchestrator AND sub-agents (by direct path reference) |
| 2 | Orchestration workflows | The four files under workflows/ |
Orchestrator only |
| 3 | Router | This SKILL.md |
Orchestrator only |
Workflows in Tier 2 sequence Tier 1 skills with gates and verification. They never duplicate Tier 1 content — they direct to it. A workflow file says "Phase N: agent reads and runs framework-skills/git-wrapup/SKILL.md," not "here's how to wrap up a release."
The orchestrator is the agent driving the workflow — the one reading this SKILL.md. Sub-agents the orchestrator spawns receive prompts pointing at Tier 1 skills directly; they do not receive this skill or the workflow file. That boundary prevents recursive sub-agent spawning.
Pick a Workflow
Identify the workflow from user intent first, then sanity-check against project state if intent is ambiguous.
| User intent / state signal | Workflow |
|---|---|
New scaffold(s) from bunx @cyanheads/mcp-ts-core init, no implementation yet (echo definitions still present, no released changelog) |
workflows/greenfield-build.md |
Existing server(s), bun outdated shows updates, want to land them and ship |
workflows/maintenance-release.md |
| Existing server(s), want to find bugs via live testing and fix them, optionally ship | workflows/field-test-fix.md |
| Existing server(s) with known issues (GH issues, handoff document, observed gap), want to fix and ship | workflows/fix-wrapup-release.md |
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.
- 4d ago Changed 9c0d7e08f3fb
- 21d ago Changed · +1 lines a33e61715bcb
- 1mo ago Changed · +11 lines dae9e2a258cd
- 2mo ago First seen · 228 lines · 159 tokens per session scan A b6a53442b543
orchestrations is a skill published in the GitHub repository cyanheads/openfoodfacts-mcp-server (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 159 tokens to every session and 5,680 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrations, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
open-meteo-guide
Tool choice, gates, and workflows for the openmeteo weather tools, covering threshold odds from the ensemble, frost, anomalies against a normal, 2050 projections, surf spots, river flood outlooks, and air quality for a set hour. Use before answering a weather, climate, marine, river, or air-quality question from…
orcid-guide
Gates, identifier chains, and Solr query syntax for the orcid tools. Use when pinning an author name, DOI, grant number, or institution to an ORCID iD, building a researcher dossier, filtering works by type or year, following put-codes to abstracts and contributors, or writing a raw ORCID query.
ensembl-guide
Gates and identifier chains for the ensembl tools. Covers checking a coordinate's assembly before you pass it in, finding a gene's counterpart in another species through homology, reading multi-allelic and capped VEP results, and which Ensembl object holds the UniProt, RefSeq, GO, and PDB references. Use when an…
noaa-spaceweather-guide
Judgment for the noaaspaceweather tools — turning SWPC Kp, storm scales, solar wind, flares, and alerts into answers about aurora visibility tonight, coming geomagnetic storms, radio blackouts, and impacts on HF radio, GPS, satellites, and power grids. Use before answering an aurora or space-weather question with…
openchargemap-guide
Assess EV charging options with openchargemap tools. Use when recommending a compatible, accessible charger, checking conflicting reliability evidence, or deciding whether a station search covers the requested area.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.