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/ci-cdnpx skills add vmkteam/claude-plugins --skill ci-cdgit clone --depth 1 https://github.com/vmkteam/claude-pluginsWhat 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.00055 | $0.00389 |
| Opus 5 | $0.00028 | $0.00195 |
| Sonnet 5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
ci-cd 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 2d 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.
What it actually says
CI/CD — Pipeline и Deploy
GitLab CI + Docker + Nomad. Pipeline настроен автоматически, вмешательство не требуется.
Ветвление и деплой
| Ветка | Окружение | Deploy |
|---|---|---|
devel |
Dev/Staging | Автоматический (merge/push → deploy) |
master |
Production | Автоматический (merge/push → deploy) |
| остальные | — | Только CI (lint/test/security) |
Nomad
Конфиги деплоя в deployments/:
deployments/
├── service.devel.nomad.hcl # Job spec для devel
├── service.master.nomad.hcl # Job spec для production
├── devel.vars.hcl # Переменные devel (count, cpu, memory)
└── master.vars.hcl # Переменные production
Переменные в .vars.hcl — ресурсы (cpu, memory), количество инстансов (count), версия образа.
CI Pipeline (справочно)
Стадии: lint → test → security → build → deploy.
Security checks:
| Инструмент | Что проверяет |
|---|---|
gitleaks |
Утечки секретов |
gosec |
Уязвимости в Go коде |
govulncheck |
Уязвимости в зависимостях |
trivy |
Уязвимости в Docker образах |
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.
- 2d ago First seen · 44 lines · 55 tokens per session scan A a46f1578a039
ci-cd is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 389 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.