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 agentmods add skills/meteor/agent-skills/skill-maintenancenpx skills add meteor/agent-skills --skill skill-maintenancegit clone --depth 1 https://github.com/meteor/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/meteor/agent-skills/skill-maintenance)<a href="https://agentmods.dev/skills/meteor/agent-skills/skill-maintenance"><img src="https://agentmods.dev/badge/skills/meteor/agent-skills/skill-maintenance.svg" alt="Measured on agentmods" 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.00054 | $0.01671 |
| Opus 5 | $0.00027 | $0.00835 |
| Sonnet 5 | $0.00011 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
skill-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 6d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Meteor agent skills
Create focused, verifiable skills for Meteor application developers. Preserve the repository contract and avoid turning the catalog into a copy of the documentation.
Scope
Published skills live under skills/. Maintainer workflows live under .github/skills/ and are not release artifacts.
Before editing:
- Read
AGENTS.mdcompletely. - Read
templates/SKILL.template.mdfor a new skill. - Read the target skill, its references, and its evaluation cases for an update.
- Inspect neighboring skills before changing routing or scope.
Do not copy maintainer skills from a Meteor source checkout into the public catalog. They describe framework contributor workflows, while this repository serves application developers.
Resolve a Meteor checkout
Resolve a checkout only when factual verification needs Meteor documentation, source, or tests.
- Prefer a path supplied by the user or task.
- Otherwise, use
METEOR_CHECKOUTwhen it is set. - Otherwise, inspect accessible workspace roots and direct sibling directories for candidates.
- Validate a candidate with
git -C <path> rev-parse --show-toplevel. Confirm thatv3-docs/,packages/, andtools/exist. Prefer a Git remote that points tometeor/meteor; allow a fork when its upstream or structure is clear. - Use an automatically discovered path only when exactly one candidate is credible. Report the resolved path.
- If no candidate or multiple candidates remain, ask the user for the Meteor checkout path. Do not clone a repository without authorization.
Never embed a machine-specific checkout path in a published skill.
Evidence order
Use evidence in this order:
- Current Meteor 3 documentation under the resolved checkout's
v3-docs/. - Meteor implementation and tests when documentation is ambiguous.
- Meteor checkout skills as navigation and maintenance guidance.
- Official release notes and pull requests for version-specific context.
- Community material only as labeled supporting context.
What ships with it
1 file 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.
- 6d ago First seen · 144 lines · 54 tokens per session scan A 6e38c95b4a94
skill-maintenance is a skill published in the GitHub repository meteor/agent-skills (7 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,671 once invoked, about $0.0003 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…