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 vmkteam/claude-plugins --skill testinggit 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/testing)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/testing"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/testing"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/testing.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.02684 |
| Opus 5.5 | $0.00037 | $0.01074 |
| Sonnet 5.5 | $0.00019 | $0.00537 |
| Haiku 4.5 | $0.00009 | $0.00268 |
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 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing — паттерны тестирования
Паттерны тестирования для vmkteam Go-сервисов.
Принципы
- Фреймворк — как в соседних
*_test.goпакета: стили в одном пакете не смешивай. В новых пакетах и проектах —t.Run+testify/assert+testify/require, table-driven для множественных кейсов. Существующие goconvey-тесты не переписывай ради переписывания - Без моков — тестируем реальный транспорт, реальную базу
- TestDB префикс — тесты с БД именуются
TestDB* - test-short пропускает DB-тесты через regex
Test[^D][^B] - Покрытие — happy path и ошибочные пути: пустой ввод, слишком длинный, граничные значения, отсутствующая запись, повторный вызов. Непокрытый ошибочный путь — дыра
- Create проверяет поля базы — не только id и эхо входа, но и то, что заполняет база:
createdAt, значения по умолчанию, вычисляемые колонки (сгенерированныйAddих не возвращает, см. /mfd) - Инварианты — если в задаче есть числовой или глобальный инвариант («≤ N», «суммарно», «во всех ветках»), первым пиши тест на худший случай (максимум полей, длины, количества) и убедись, что он падает на старом коде
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.
- 6d ago Changed · +17 lines 215649cb611e
- 23d ago Changed · +80 lines · +41 tokens per session fff5e01e7a58
- 1mo 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 6d ago), licensed MIT. It adds 93 tokens to every session and 2,684 once invoked, about $0.0004 per session on Opus 5.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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.