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 meteor/agent-skills --skill skill-gap-auditgit 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-gap-audit)<a href="https://agentmods.dev/skills/meteor/agent-skills/skill-gap-audit"><img src="https://agentmods.dev/badge/skills/meteor/agent-skills/skill-gap-audit.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.00068 | $0.01175 |
| Opus 5 | $0.00034 | $0.00588 |
| Sonnet 5 | $0.00014 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
skill-gap-audit 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Meteor skill gaps
Compare the published catalog with current Meteor documentation and implementation. Produce a prioritized maintenance report. Do not create or edit skills during the audit.
This workflow adapts Meteor's docs-gap and changelog skill patterns while keeping the checkout path, checked-out branch, release context, and comparison revisions configurable.
Inputs
Determine these inputs before analysis:
- Agent-skills repository root.
- Meteor source checkout.
- Audit mode: full catalog or incremental changes.
- Base and target Git revisions for an incremental audit.
- Meteor version or release context when the audit targets a release.
- Optional previous committed audit record.
- Optional output path. Return the report in the response when no path is requested.
Resolve the Meteor checkout
- 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 each candidate with
git -C <path> rev-parse --show-topleveland requirev3-docs/,packages/, andtools/. Use Git remotes to distinguishmeteor/meteoror a clear fork from unrelated repositories. - Continue automatically only when one credible candidate remains. Report its resolved path, remote, branch, commit SHA, and dirty state.
- Ask the user for a checkout path when discovery finds none or remains ambiguous. Do not assume a home directory layout or clone without authorization.
The checkout can live anywhere accessible in the current environment. Do not store its machine-specific absolute path in committed skill content.
Audit method
Read references/audit-method.md before gathering evidence. It defines committed baselines, full, release, and incremental modes, changelog and release review, deep distributable-claim comparison, and source filtering.
Build the skill inventory
For every publishable folder under skills/:
What ships with it
2 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.
- 6d ago First seen · 108 lines · 68 tokens per session scan A 0e6220e93d77
skill-gap-audit is a skill published in the GitHub repository meteor/agent-skills (7 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 1,175 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…
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…