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/melodic-software/claude-code-plugins/checknpx skills add melodic-software/claude-code-plugins --skill checkgit clone --depth 1 https://github.com/melodic-software/claude-code-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/melodic-software/claude-code-plugins/check)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/check"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/check.svg" alt="Measured on agentmods" 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 | $0.00209 | $0.02203 |
| Opus 5 | $0.00105 | $0.01102 |
| Sonnet 5 | $0.00042 | $0.00441 |
| Haiku 4.5 | $0.00021 | $0.00220 |
Grade A, and why
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 yesterday.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
!"${CLAUDE_PLUGIN_ROOT}/scripts/precompute.sh" check 2>/dev/null || echo "- Orientation unavailable"
Purpose
A gate, not an audit. It answers one question with one exit code: would every path-scoped instruction surface in this repository actually load when it is supposed to, and does the always-loaded index still describe what is on disk?
It exists because every failure mode here is silent. Claude Code does not warn when a rule's glob matches nothing, when a bracket expression is malformed, or when a pattern exceeded the brace budget and was used unexpanded. The rule simply never fires, and the convention it carries is quietly absent from every session that needed it. A repository can accumulate a dozen dead rules and look perfectly healthy.
Wire it into CI beside the linters. It is fast, deterministic, and has no judgment layer to drift.
What it checks
| Check | Mechanism | Failure means |
|---|---|---|
| Glob resolves | glob-tools.sh rules |
The rule never fires for any file in the repository |
| Bracket expressions valid | same | The pattern silently matches nothing |
| Brace budget respected | same | The pattern is used unexpanded; its braces match nothing |
| Glob not over-broad | same | Advisory. The rule loads so often it saves nothing |
| Index in sync | render-index.sh check |
Deferred surfaces are unreachable from subagents |
| Index target loaded at all | render-index.sh reachable |
The index exists and Claude Code never reads it |
The last one is the newest and the least obvious. Claude Code reads CLAUDE.md, not AGENTS.md. A
repository carrying both with no import between them gets a perfectly-generated, perfectly-in-sync
index that never enters context, the entire subagent-gap mitigation doing nothing while every other
check reports green. Sync and reachability are independent questions; ask both.
Over-broad is the one warning rather than a failure: breadth is a judgment about whether a demotion was worth making, not a statement that the rule is broken. Everything else is a hard fail.
What ships with it
1 file 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.
- yesterday First seen · 158 lines · 209 tokens per session scan A 633b918d7262
check is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), licensed MIT. It adds 209 tokens to every session and 2,203 once invoked, about $0.0010 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-09-03.
Other skills, from other repositories
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
structuring-documentation
Use when writing, editing, auditing, splitting, or measuring Markdown documentation surfaces — README.md, AGENTS.md, CLAUDE.md, and docs/ siblings. Triggers include "is this doc too long", "split this README", "measure the docs", "where does this documentation belong", "audit the documentation", and any request to…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…
phpunit-migration-test-generation
Use this skill when the user asks to generate, write, or create migration tests for a Shopware 6 migration class — phrases like "generate migration tests", "write a migration test", "create migration test", "test this migration", "test Migration1234Foo". Analyzes the source migration's SQL operations to pick an…
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…