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 maintenancegit 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/maintenance)<a href="https://agentmods.dev/skills/cyanheads/openfoodfacts-mcp-server/maintenance"><img src="https://agentmods.dev/badge/skills/cyanheads/openfoodfacts-mcp-server/maintenance/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/maintenance"><img src="https://agentmods.dev/badge/skills/cyanheads/openfoodfacts-mcp-server/maintenance.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.00075 | $0.05739 |
| Opus 5.5 | $0.00030 | $0.02296 |
| Sonnet 5.5 | $0.00015 | $0.01148 |
| Haiku 4.5 | $0.00007 | $0.00574 |
Grade A, and why
maintenance 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 yesterday.
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 maintenance — 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- After running
bun update --latestyourself and wanting to review the impact (Mode B — typical) - To run the whole flow end-to-end — outdated check → update → investigate → adopt → verify (Mode A)
- Periodically, to check for skill drift from the package
Entry Modes
| Mode | Starting Point | First Step |
|---|---|---|
| A — Full flow | Lockfile is current; want to update | Step 1 |
| B — Post-update review | User already ran bun update --latest + bun run rebuild + bun run test |
Skip to Step 3 with the update output or a bun.lock diff |
Both modes converge at Step 3 and end at Step 8.
Steps
1. Survey what's outdated (Mode A only)
bun run devcheck --only outdated
Wraps bun outdated with the project's devcheck.config.json allowlist applied, so intentionally-pinned packages don't surface as actionable. Plain bun outdated works too if you want the unfiltered view.
Note: bun update --latest crosses semver majors; bun update alone respects ranges. Use --latest unless a package is intentionally pinned.
2. Apply the update (Mode A only)
bun update --latest
Capture the ↑ package old → new lines from stdout — these feed Step 3. Alternatively, diff bun.lock to surface version deltas after the fact.
3. Investigate changelogs
Invoke the changelog skill with the captured list of updated packages. It resolves each repo, fetches release notes (or CHANGELOG entries) between old and new versions, and cross-references changes against actual imports in src/. Output per package: what changed, impact on this project, action items.
Do not redo this investigation inline — the changelog skill handles tag-format detection, monorepo patterns, and fallbacks. If the skill cannot resolve a package (private repo, no tags, no CHANGELOG), note it in Step 8 under "Open decisions" and proceed.
4. Framework review (@cyanheads/mcp-ts-core)
Skill-version paradox. If node_modules/@cyanheads/mcp-ts-core/framework-skills/maintenance/SKILL.md's version exceeds the one running, run Step 5 Phase A first and re-invoke maintenance — otherwise feature-adoption rows added in the new version silently don't surface. After Phase A, confirm the running skill version matches the package before continuing. If the session still has the old skill loaded, exit and restart.
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.
- yesterday Changed ea6cae335890
- 21d ago Changed 193bb6f9e2d0
- 1mo ago Changed · +10 lines 200b10ae5f82
- 2mo ago First seen · 243 lines · 75 tokens per session scan A d86eacb0aa5a
maintenance is a skill published in the GitHub repository cyanheads/openfoodfacts-mcp-server (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 75 tokens to every session and 5,739 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to maintenance, 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.