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/qte77/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/qte77/claude-code-plugins/tdd-core)<a href="https://agentmods.dev/plugins/qte77/claude-code-plugins/tdd-core"><img src="https://agentmods.dev/badge/plugins/qte77/claude-code-plugins/tdd-core/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/plugins/qte77/claude-code-plugins/tdd-core"><img src="https://agentmods.dev/badge/plugins/qte77/claude-code-plugins/tdd-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tdd-core 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 25d 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
{
"name": "tdd-core",
"version": "1.0.2",
"description": "Language-agnostic TDD methodology: Red-Green-Refactor cycle, Arrange-Act-Assert, testing strategy, anti-patterns",
"author": { "name": "Claude Code Utils Contributors" },
"keywords": ["tdd", "testing", "red-green-refactor", "arrange-act-assert", "test-driven"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 37 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 25d ago Changed 36798b76aebf
- 1mo ago First seen · 8 lines scan A 241374fd53a9
tdd-core is a plugin published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. 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
vbounce
V-Bounce AI-Native SDLC Orchestrator v5.1 — Agent-first architecture with unified TDD, per-phase specialized QG agents, mixed-model assignment, tech-aware context injection, explicit contracts, shared workspace, state management, and multi-layer quality assurance for complete software development lifecycle.
go-specialist
Master Go 1.25+ development with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Skills: gen-forgejo-dir, gen-github-dir, gen-gitlab-ci, gen-goreleaser, gen-linter, gen-taskfiles, go-blackbox, go-bulma, go-structure, go-tdd, go-tool. MCP: context7.
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.
golang
Modern Go development — stdlib-first code style with cobra/viper CLIs, table-driven tests and native fuzzing, canonical project layout with pinned tooling, documentation conventions with LLM-ready CLI references, and GoReleaser-based release engineering.
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.
engineering-practices
Git commits, conventional releases, refactoring, test-driven development, and engineering ways of working skills.