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 michael-harris/devteamnpx agentmods add plugins/michael-harris/devteam/marketplacegit clone --depth 1 https://github.com/michael-harris/devteamGrade A, and why
devteam-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 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://anthropic.com/claude-code/marketplace.schema.json",
"name": "devteam-marketplace",
"owner": {
"name": "michael-harris",
"email": "[email protected]"
},
"metadata": {
"description": "Marketplace for the DevTeam plugin",
"version": "4.0.0"
},
"plugins": [
{
"name": "devteam",
"description": "127-agent automated development system with Agent Teams, quality gates, Bug Council diagnostics, and autonomous execution",
"version": "4.0.0",
"source": "./",
"author": {
"name": "Multi-Agent Development Team",
"email": "[email protected]"
},
"category": "development",
"tags": ["development", "automation", "multi-agent", "orchestration", "quality-gates", "testing", "security", "autonomous"],
"repository": "https://github.com/michael-harris/devteam",
"license": "MIT"
}
]
}
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.
- yesterday First seen · 29 lines scan A ffe5b8f8db8f
devteam-marketplace is a plugin published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo 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
ops
Structured non-code project management for Claude Code: planning, execution, knowledge persistence, and autonomous work loops for research, strategy, and content projects. 9 skills, 5 agents, 7 commands.
factory-kit
Portable Factory Kit workflows for software delivery.
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.
web-dev
Multi-agent web dev pipeline — UX research and design critique around the build, plus the designer ↔ frontend contract: freeze approved mockups into a canonical oracle, port them 1:1 on any stack, and verify with screenshot-based design-diff gates.
context-engineering
Context engineering for AI agents — AI-optimized second-brain skills, durable pipeline state for multi-agent handoffs, and expert prompt building.
dotforge
Behavior governance for Claude Code — declarative runtime policies on tool calls (search-first, no-destructive-git, verify-before-done, …) compiled to PreToolUse hooks, plus configuration governance: 18 skills, 7 agents, 16 stacks, audit scoring, practices pipeline.