Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add spumer/i-m-senior-developer/plugin install plugin-testingWrote 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/spumer/i-m-senior-developer/plugin-testing)<a href="https://agentmods.dev/skills/spumer/i-m-senior-developer/plugin-testing"><img src="https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/plugin-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/spumer/i-m-senior-developer/plugin-testing"><img src="https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/plugin-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.00163 | $0.01554 |
| Opus 5.5 | $0.00065 | $0.00622 |
| Sonnet 5.5 | $0.00033 | $0.00311 |
| Haiku 4.5 | $0.00016 | $0.00155 |
Grade A, and why
plugin-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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Проверка поведения плагинов Claude Code
Скилл ведёт работу с проверками плагинов: от выбора вида проверки до разбора красного прогона и записи отчёта. Опирается на измеренные факты, а не на предположения о поведении модели.
Что выбрать: структура или поведение
Сначала определить вид проверки, иначе усилия уйдут не туда.
| Вопрос | Инструмент | Стоимость |
|---|---|---|
| Плагин загрузится, манифест и frontmatter валидны? | claude plugin validate --strict |
бесплатно |
| Скилл срабатывает и ведёт работу правильно? | claude plugin eval |
платно |
| Детерминированная функция даёт нужный результат? | обычный тест рядом с исходником | бесплатно |
Не писать eval для того, что проверяет обычный тест. Eval нужен только там, где результат существует лишь в поведении модели.
Полный набор вызовов структурной проверки и её измеренные границы —
references/validate.md.
Шаг 0. Предусловия
До любого платного прогона убедиться в двух вещах.
Гейт раннего доступа открыт. Проверять в пустом каталоге:
tmpdir=$(mktemp -d)
(cd "$tmpdir" && claude plugin eval)
No eval cases found — открыт, currently in early access — закрыт. Природа
гейта и его включение — references/early-access.md.
Версия CLI закреплена. Обновление меняет и формат результата, и поведение
модели. Порядок закрепления версии в непрерывной сборке —
references/validate.md.
Шаг 1. Сформулировать наблюдаемый договор
Для каждого кейса ответить на четыре вопроса:
- какой вход даёт человек;
- какое поведение обязательно наступает;
- что из этого наблюдаемо снаружи — вызов инструмента, файл, финальный ответ;
- какая ошибочная реализация обязана уронить проверку.
Без конкретных ответов кейс не обоснован.
Шаг 2. Собрать кейс
Кейс — каталог под evals/ плагина: prompt.md с параметрами запуска и
graders/*.md с критериями. Формат, шесть типов критериев и их ловушки —
references/graders.md.
Предпочитать детерминированные критерии. Модель-судью брать только для смысла ответа.
What ships with it
9 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.
- references/deterministic-routing.md 4.4 KB
- references/early-access.md 3.7 KB
- references/failures.md 5.5 KB
- references/graders.md 6.3 KB
- references/report.md 5.3 KB
- references/validate.md 4.0 KB
- references/wrapper.md 7.6 KB
- scripts/check_eval_suite.py 6.0 KB runs code
- scripts/test_check_eval_suite.py 5.0 KB runs code
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.
- 1mo ago First seen · 139 lines · 163 tokens per session scan A e211abe86ffe
plugin-testing is a skill published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 3d ago), licensed MIT. It adds 163 tokens to every session and 1,554 once invoked, about $0.0007 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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.