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/gowtham012/Claude-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/gowtham012/claude-plugins/deep-engineer)<a href="https://agentmods.dev/plugins/gowtham012/claude-plugins/deep-engineer"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/deep-engineer/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/gowtham012/claude-plugins/deep-engineer"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/deep-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deep-engineer 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-engineer",
"description": "Forces Claude through a disciplined engineering loop: generalize the problem, think through scenarios, TDD, implement, verify. Prevents hardcoded solutions and skipped edge cases.",
"version": "1.1.0",
"author": { "name": "Gowtham" },
"license": "MIT",
"homepage": "https://github.com/gowtham012/Claude-plugins/tree/main/deep-engineer",
"repository": "https://github.com/gowtham012/Claude-plugins",
"keywords": ["tdd", "engineering", "testing", "autonomous", "loop", "discipline"]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 55 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 · 11 lines scan A eab49ab2c126
deep-engineer is a plugin published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 7mo 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-31.
Other plugins, from other repositories
supergraph
Evidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.10.8,<0.11.0 with optional Serena LSP intelligence, 7 specialized subagents, and native Rust CDP browser/API automation. Includes blast-radius planning, test/cycle gates, independent…
pdlc
Turn AI software engineering into an auditable, on-disk state machine. A staged PDLC workflow (PRD, design, TDD, implement, review, ship, retro) enforces hard contracts — artifacts on disk, per-feature state machine, tests-before-code, objective checks from real command exit codes, single-shot auto-repair — so AI work.
aiagentminder
An opinionated governance layer for Claude Code, built for solo developers: autonomous sprint execution in isolated git worktrees, mandatory TDD, quality gates, pre-PR code review, and structured planning — workflow enforced by hooks, not just rules.
ConsiderateCoder
Development methodology plugin: Clean Architecture x TDD x three-tier delegation (communicator / orchestrator / worker) with /plan-sdd, /outsource, /dig and /refactor commands.
autocode-flow
Autonomous dev pipeline generator. /autocode-flow:autocode-new scans & configures, /autocode-flow:autocode auto-executes plan → tdd → code → test → verify with zero human intervention.
forge
A Claude Code plugin for upgrading skills with test-driven development (TDD), which means checking expected results as part of making changes.