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-projectWrote 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-project/marketplace)<a href="https://agentmods.dev/plugins/piercelamb/deep-project/marketplace"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-project/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-project/marketplace"><img src="https://agentmods.dev/badge/plugins/piercelamb/deep-project/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.
Copies of this mod
2 near-identical copies found in the catalogue:
- piercelamb-plugins marketplace — 100% identical, 10 lines differ
- piercelamb-plugins marketplace — 100% identical, 10 lines differ
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": "./",
"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": {
"source": "url",
"url": "https://github.com/piercelamb/deep-plan.git"
},
"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 the loThe 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 c4bec3e822c2
piercelamb-plugins marketplace is a plugin published in the GitHub repository piercelamb/deep-project (222 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
piyaz marketplace
Plugin marketplace listing 1 plugin: piyaz.
piyaz
Persistent context network for coding projects. Tracks tasks, dependencies, and decisions across sessions.
field-guide
Distills useful project understanding into a persistent, searchable wiki in .lore/reference/. Sibling to lore-development.
compass-rose
A file-based issue tracker for solo projects. Zero config, no GitHub required. Issues live in .lore/work/issues/ alongside your code.
lore-development
A lightweight plugin for building project context. Skills for research, brainstorming, intent, design, planning, implementation, and retrospectives.
mind-reader
Active feedback based on session patterns and sentiment analysis.