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/testingnpx skills add vmkteam/claude-plugins --skill testinggit 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.00052 | $0.01454 |
| Opus 5 | $0.00026 | $0.00727 |
| Sonnet 5 | $0.00010 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
testing 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing — паттерны тестирования
Паттерны тестирования для vmkteam Go-сервисов.
Принципы
- Канонический стиль —
t.Run+testify/assert+testify/require. Table-driven для множественных кейсов - Legacy на goconvey — не переписывай ради переписывания, но новые тесты в таких проектах тоже на
t.Run+ testify - Без моков — тестируем реальный транспорт, реальную базу
- TestDB префикс — тесты с БД именуются
TestDB* - test-short пропускает DB-тесты через regex
Test[^D][^B]
Makefile targets
# Все тесты (включая DB)
test:
@PGDATABASE=$(TEST_PGDATABASE) go test -count=1 $(GOFLAGS) -coverprofile=coverage.txt -covermode count $(PKG)
# Быстрые тесты (без DB) — пропускает TestDB*
test-short:
@go test $(GOFLAGS) -v -test.short -test.run="Test[^D][^B]" -coverprofile=coverage.txt -covermode count $(PKG)
# Пересоздать тестовую БД
db-test:
@dropdb --if-exists $(TEST_PGDATABASE)
@createdb -E UTF-8 $(TEST_PGDATABASE)
@psql -f docs/schema.sql $(TEST_PGDATABASE)
Канонический стиль (t.Run + testify)
import (
"testing"
"github.com/stretchr/testify/assert"
"github.com/stretchr/testify/require"
)
func TestDBUserService(t *testing.T) {
ctx := t.Context()
srv := NewUserService(testDB)
t.Run("CRUD", func(t *testing.T) {
in := User{
Login: fmt.Sprintf("ivan_%d", time.Now().Unix()),
Password: "pwd",
StatusID: db.StatusEnabled,
}
out, err := srv.Add(ctx, in)
require.NoError(t, err)
require.NotNil(t, out)
assert.Greater(t, out.ID, 0)
got, err := srv.GetByID(ctx, out.ID)
require.NoError(t, err)
assert.Equal(t, in.Login, got.Login)
got.Login = "updated"
ok, err := srv.Update(ctx, *got)
require.NoError(t, err)
assert.True(t, ok)
ok, err = srv.Delete(ctx, out.ID)
require.NoError(t, err)
assert.True(t, ok)
})
t.Run("empty login is rejected", func(t *testing.T) {
_, err := srv.Add(ctx, User{Login: "", Password: "pwd", StatusID: db.StatusEnabled})
require.Error(t, err)
})
}
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 · 176 lines · 52 tokens per session scan A 51d20439f724
testing is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,454 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…