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/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/claude-code-plugin)<a href="https://agentmods.dev/plugins/jeremydev87/codingbuddy/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/jeremydev87/codingbuddy/claude-code-plugin/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/jeremydev87/codingbuddy/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/jeremydev87/codingbuddy/claude-code-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codingbuddy 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 1mo 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": "codingbuddy",
"version": "5.6.3",
"description": "PLAN/ACT/EVAL workflow with auto-detection, specialist agents, and reusable skills for systematic TDD development",
"author": {
"name": "JeremyDev87",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 6 commands, 4 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 19 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command eval A 0 tokens
- Command plan A 0 tokens
- Command act A 0 tokens
- Command auto A 0 tokens
- Command buddy A 19 tokens
- Command checklist A 0 tokens
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- MCP server codingbuddy A not measured
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.
- 1mo ago First seen · 10 lines scan A da0b55a0fa35
codingbuddy is a plugin published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. 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-08-30.
Other plugins, from other repositories
ring marketplace
Lerian Studio plugin marketplace: Core software engineering skills (TDD, debugging, code review), specialized developer agents (Backend, DevOps, Frontend, QA, SRE) plus 12 code-review reviewers (9 default hard-gate reviewers and 3 conditional stack specialists), product planning workflows (8-gate pre-dev system), and…
ring-default
Core skills library from the Lerian Team: TDD, code review, collaboration patterns, and proven techniques. 23 essential skills for software engineering excellence, including plan authoring and execution.
aegis
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques.
don-cheli-sdd
Full SDD (Spec-Driven Development) framework for Claude Code. 72+ slash commands (/dc:), 14 reusable skills, 15 reasoning models, TDD as an iron law, and i18n support (ES/EN/PT). Turn requirements into tested, documented, production-ready code through 7 disciplined lifecycle phases.
sdlc-wizard-cowork
SDLC enforcement for Claude Cowork — TDD, planning, self-review via skills and one prompt-based hook.
pdca
TDD-disciplined AI code generation using Plan-Do-Check-Act methodology. Enforces architecture-first analysis, strict red-green-refactor, Socratic ACT retrospectives, and optional Beads task tracking integration.