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.
git clone --depth 1 https://github.com/bengous/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/commands/bengous/claude-code-plugins/test-layer)<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/test-layer"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/test-layer/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/commands/bengous/claude-code-plugins/test-layer"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/test-layer.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.00007 | $0.00293 |
| Opus 5.5 | $0.00003 | $0.00117 |
| Sonnet 5.5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
test-layer 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 7d 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.
What it actually says
Test Layer
Test a specific architectural layer with comprehensive coverage analysis.
Usage
/test-layer <module> <layer> [playbook] [--coverage <N>]
Examples:
/test-layer auth infrastructure
/test-layer auth infrastructure docs/playbook.md
/test-layer auth infrastructure docs/playbook.md --coverage 80
Natural invocation:
- "Test the infrastructure layer of auth"
- "Test auth/infrastructure with my playbook"
Your Task
Step 1: Parse Arguments
Extract from $ARGUMENTS:
- MODULE:
$1 - LAYER:
$2 - PLAYBOOK:
$3(optional) - COVERAGE: from
--coverage <N>flag (optional)
Step 2: Invoke Skill
Skill(skill: "claude-orchestration:layer-testing")
Step 3: Provide Context
Testing Request:
- Module: <MODULE>
- Layer: <LAYER>
- Playbook: <PLAYBOOK or "none">
- Coverage Target: <COVERAGE>% (when `--coverage` is not given: the strategy's target for the layer)
Done. The skill handles the rest.
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.
- 7d ago Changed 58e7d6424c1e
- 1mo ago Changed 0a28f6a79df9
- 1mo ago First seen · 56 lines · 7 tokens per session scan A 5fb4fa0103b1
test-layer is a command published in the GitHub repository bengous/claude-code-plugins (6 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 293 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
test-generate
Generate and run tests [file].
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.