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 mgiovani/cc-arsenal --skill vrt-checkgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/vrt-check)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/vrt-check"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/vrt-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00180 | $0.01912 |
| Opus 5 | $0.00090 | $0.00956 |
| Sonnet 5 | $0.00036 | $0.00382 |
| Haiku 4.5 | $0.00018 | $0.00191 |
Grade A, and why
vrt-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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VRT Check
Run visual regression tests, then triage every failure by eye before touching a snapshot. The workflow's only real risk is rubber-stamping --update on a diff nobody looked at: everything below exists to prevent that.
Step 1: Discover the tooling
Never assume a command. Different repos wire VRT through different tools. Look for, in order:
- Task runner targets:
just --listorgrep -E 'visual|screenshot|chromatic|snapshot' justfile Makefilefor targets likevisual-diff,visual-update,test:visual. - package.json scripts:
grep -A2 '"scripts"' package.jsonforchromatic,test:visual,storybook:test,playwright test.*visual. - Storybook test-runner: presence of
.storybook/test-runner.tsor@storybook/test-runnerinpackage.json. - Playwright screenshot tests:
toHaveScreenshot(calls in*.spec.ts, or aplaywright.config.*withsnapshotDir/toMatchSnapshotsettings. - Chromatic:
chromatic.config.jsonor achromaticdevDependency; these run in CI and produce a web UI, not local diff images, say so and point the user there instead of trying to fake a local diff. - Loki:
.lokiconfig orlokidevDependency.
Base each check on the actual output of the command you ran (ls, grep, just --list), never assert a file is absent without having listed the directory. If two of these are present, ask the user which one is authoritative rather than running both. If none are found, stop and say so, do not invent a screenshot workflow.
For an unfamiliar repo, where a subagent/Task tool is available, delegate this discovery to it rather than grepping inline yourself; otherwise run the greps above directly. Either way, keep the discovered commands around for the rest of the run.
Step 2: Run the diff
Run the discovered diff target, not the update target, even if the user asked to "fix the visual tests", you need to see what changed before deciding anything should be updated.
just visual-diff # or whatever Step 1 found
What ships with it
2 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.
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.
- 8d ago First seen · 101 lines · 180 tokens per session scan A 1b2d0d2dff07
vrt-check is a skill published in the GitHub repository mgiovani/cc-arsenal (7 stars, last pushed 8d ago), licensed MIT. It adds 180 tokens to every session and 1,912 once invoked, about $0.0009 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
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
safe-rename
Workflow for safely renaming symbols (functions, types, classes, interfaces, constants, variables) across a codebase. Uses repomap, batchsymbols, and buildcheck to ensure every consumer is updated and nothing breaks.
test-file-split
Protocol for splitting test files that approach or exceed the FR-006 500-line limit (enforced in CI by scripts/check-test-file-cap.ts as a diff-scoped ratchet). Covers describe-block extraction, shared helper management, pure-function extraction, mock isolation verification, and cascading-split detection. Load when a…
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.