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/vmkteam/claude-plugins/skills-checknpx skills add vmkteam/claude-plugins --skill skills-checkgit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/vmkteam/claude-plugins/skills-check)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/skills-check"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/skills-check.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 | $0.00040 | $0.01192 |
| Opus 5 | $0.00020 | $0.00596 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
skills-check 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skills-check — smoke-тесты интеграций
Быстрая проверка, что внешние системы, описанные в project-index.md и infra-{group}.md, отвечают на канонические запросы data-source скиллов. Нужен когда URL/API провайдеров могли измениться, токены истечь или профили pcurl разойтись со skill-конвенциями.
Использование
/skills-check # все настроенные интеграции
/skills-check youtrack gitlab # только перечисленные
/skills-check --verbose # печатать полный ответ, а не только HTTP-код
Что проверяется
Читает {project-auto-memory}/project-index.md и подключённый infra-файл. Для каждой секции запускает минимальный пробник:
| Секция | Проба | OK-признак |
|---|---|---|
| YouTrack | GET /api/admin/projects?fields=id&$top=1 |
HTTP 200, [] массив |
| GitLab | GET /api/v4/projects/{gl_project_id}?simple=true |
HTTP 200, .id |
| Sentry | GET /api/0/organizations/{org}/projects/?per_page=1 |
HTTP 200 |
| Grafana | GET /api/datasources |
HTTP 200, массив |
| Prometheus (Grafana proxy) | GET /api/datasources/uid/{uid}/resources/api/v1/labels |
HTTP 200, .status=="success" |
| Loki (Grafana proxy) | GET /api/datasources/uid/{uid}/resources/labels |
HTTP 200, .status=="success" |
| Kibana/OpenSearch | GET /api/status с osd-xsrf: true |
HTTP 200 |
| Nomad | GET /v1/status/leader |
HTTP 200 |
| API dev/prod | GET {rpc_endpoint}?smd |
HTTP 200, валидный JSON с .services |
Также кросс-проверяется, что все упомянутые в project-index pcurl-профили есть в pcurl show — несовпадение = профиль не создан локально.
Порядок выполнения
- Прочитать
project-index.mdиinfra-{group}.md - Собрать список (скилл, профиль, URL, ожидаемый shape)
- Запустить пробники параллельно (через
&+waitили через xargs) - Собрать результаты в таблицу
Шаблон пробника
# Шаблон: silent, только HTTP-код + время
pcurl @{profile} '{url}' -s -o /dev/null -w '%{http_code} %{time_total}\n'
Для verbose — без -o /dev/null, плюс jq '.' | head -5 для первых строк ответа.
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.
- 5d ago First seen · 92 lines · 40 tokens per session scan A 55f392a7075c
skills-check is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,192 once invoked, about $0.0002 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…