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.
/plugin marketplace add melodic-software/claude-code-pluginsnpx agentmods add plugins/melodic-software/claude-code-plugins/implementationgit 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/plugins/melodic-software/claude-code-plugins/implementation)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/implementation"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/implementation.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
implementation 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "implementation",
"version": "0.16.0",
"description": "Disciplined implementation stage: execute approved plans inline (`/implementation:implement`) or via orchestrated worker subagents (`/implementation:implement-dispatch`) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back to planning. Build/test/lint, testing, and outcome verification live in the companion `toolchain`, `testing`, and `verification` plugins, invoked when installed.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"implementation",
"implement",
"orchestration",
"execution",
"tdd",
"skill"
]
}
What it installs
The manifest is a name and a version. 2 skills, 2 agents travel with it, and installing the plugin installs all of them — 354 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.
- yesterday First seen · 20 lines scan A 5404b646124c
implementation is a plugin published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), 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-09-03.
Other plugins, from other repositories
tdd-dev
Transform Claude Code into a strict TDD practitioner that enforces Red→Green→Refactor cycles.
skills
Dagster skills for CLI operations, best practices, and integrations.
crashlytics
Generate crash reports from Firebase Crashlytics for iOS and Android with fix proposals and developer assignments.
local-llm
Manage local Ollama LLM models for development and testing.
parallel-workflows
Parallel workflow orchestration using git worktrees for concurrent Claude Code sessions.
error-therapist
Audit and rewrite error messages to be helpful and actionable.