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/tomevault-io/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/plugins/tomevault-io/claude-code-plugins/biomejs-biome-testing-codegen)<a href="https://agentmods.dev/plugins/tomevault-io/claude-code-plugins/biomejs-biome-testing-codegen"><img src="https://agentmods.dev/badge/plugins/tomevault-io/claude-code-plugins/biomejs-biome-testing-codegen.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
biomejs--biome--testing-codegen 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 14 lines scan A ce44f69f9c8f
biomejs--biome--testing-codegen is a plugin published in the GitHub repository tomevault-io/claude-code-plugins (3 stars, last pushed today), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
js-ts
JavaScript and TypeScript development toolkit with ESLint, Vitest, and unit testing best practices.
ginkgo
Write, run, and debug Ginkgo/Gomega test suites in Go. Skills for the tree-construction mental model, spec authoring and cleanup, tables and generated specs, the full decorator reference, filtering, parallelism, ordered/flaky specs, timeouts and async, the CLI and CI configuration, reporting, and JSON-first failure…
vitest-auto-spy
Typed test spies from a class or a type on Vitest, bun:test and node:test — the skill teaches an agent the API, the anti-patterns, the error→fix table and the codemod that migrates a suite off jest-auto-spies or jasmine-auto-spies.
tdd-ts
TypeScript quality tools: tsc, ESLint, Prettier, Jest/Vitest.
pytest-best-practices
pytest async-first testing best practices — test layer structure, fixture design, async testing with pytest-asyncio, test data with factoryboy + faker, HTTP mocking with respx, time mocking with freezegun, property-based testing with hypothesis, DB transaction-rollback isolation, flush() pattern for chained fixtures.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.