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-planWrote 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-plan/marketplace)<a href="https://agentmods.dev/plugins/piercelamb/deep-plan/marketplace"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-plan/marketplace/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-plan/marketplace"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-plan/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
piercelamb-plugins marketplace 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.
This is a copy
100% identical to piercelamb-plugins marketplace — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "piercelamb-plugins",
"description": "Claude Code plugins by Pierce Lamb",
"version": "1.1.7",
"owner": {
"name": "Pierce Lamb",
"url": "https://github.com/piercelamb"
},
"plugins": [
{
"name": "deep-project",
"description": "Split vague project requirements into well-scoped units for /deep-plan",
"version": "0.2.1",
"author": {
"name": "piercelamb",
"url": "https://github.com/piercelamb"
},
"source": {
"source": "url",
"url": "https://github.com/piercelamb/deep-project.git"
},
"category": "development",
"homepage": "https://github.com/piercelamb/deep-project",
"tags": ["planning", "decomposition", "project-management", "requirements"]
},
{
"name": "deep-plan",
"description": "AI-assisted deep planning with research, interview, external LLM review, and TDD approach",
"version": "0.3.2",
"author": {
"name": "piercelamb",
"url": "https://github.com/piercelamb"
},
"source": "./",
"category": "development",
"homepage": "https://github.com/piercelamb/deep-plan",
"tags": ["planning", "tdd", "architecture", "llm-review", "implementation"]
},
{
"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"
},
"source": {
"source": "url",
"url": "https://github.com/piercelamb/deep-implement.git"
},
"category": "development",
"homepage": "https://github.com/piercelamb/deep-implement",
"tags": ["implementation", "tdd", "code-review", "git", "workflow"]
},
{
"name": "deep-sota",
"description": "Paper- and repo-grounded research over theThe plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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 · 90 lines scan A 092b0b844495
piercelamb-plugins marketplace is a plugin published in the GitHub repository piercelamb/deep-plan (101 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. It is 100% identical to piercelamb-plugins marketplace, differing in 10 lines, and is treated as a copy.
Other plugins, from other repositories
wyx
Architecture guardrails for Claude Code — automatically injects declared module boundaries into Claude's context when it edits files near a spec.
capstone
Architecture reference generator: a lean docs/capstone/ index plus topic files stamped to the commit they were derived at, built and kept current by one command, map. Companion commands: doctor, an opt-in two-sided review, a greenfield pipeline from mockup to running code with a frontend-design stage, and a…
capstone
Architecture reference docs: a docs/capstone/ index plus topic files stamped to commits, built and kept current by one command, map, plus doctor/review, a greenfield pipeline from product mockup to running code with a frontend-design stage, and a doc-grounded feature chain.
punchcard
Architecture-level code review from a fifty-year veteran: design, boundaries, data and error paths — never naming or formatting. One verdict, every finding that earns its place, every claim demonstrated in code. Reviews a diff in the conversation or posts one review into a GitHub PR / GitLab MR. Briefs a change before.
archlint
Catches architectural drift while the agent writes code — checks edited files' imports against layer rules declared in your CLAUDE.md.
spec-driven
Spec-driven development workflow with structured requirements, design, and task phases.