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/piercelamb/deep-implementWrote 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/piercelamb/deep-implement/deep-implement)<a href="https://agentmods.dev/plugins/piercelamb/deep-implement/deep-implement"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-implement/deep-implement/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/piercelamb/deep-implement/deep-implement"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-implement/deep-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deep-implement 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": "deep-implement",
"description": "Implement code from /deep-plan sections with TDD, code review, and git workflow",
"version": "0.2.1",
"author": {
"name": "piercelamb",
"url": "https://github.com/piercelamb"
},
"repository": "https://github.com/piercelamb/deep-implement",
"license": "MIT",
"keywords": ["implementation", "tdd", "code-review", "git", "workflow"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 57 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 13 lines scan A d98153977cfc
deep-implement is a plugin published in the GitHub repository piercelamb/deep-implement (55 stars, last pushed 3mo 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
shipyard
Ship software systematically: project lifecycle, TDD, parallel agents, code review, security auditing, and infrastructure validation.
flow
Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals…
engineering-skills
Cross-platform engineering skills across the software lifecycle, with auditable documents, task-sized workflows and self-contained Codex installation.
superpowers-orchestrator
Agentic development framework for Claude Code — disciplined workflow routing, TDD enforcement, safety hooks, systematic debugging, and code review.
engineering-practices
Git commits, conventional releases, refactoring, test-driven development, and engineering ways of working skills.
deep-plan
AI-assisted deep planning with research, interview, external LLM review, and TDD approach.