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 Surjal/dev-agentnpx agentmods add plugins/surjal/dev-agent/marketplacegit clone --depth 1 https://github.com/Surjal/dev-agentGrade A, and why
dev-agent 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": "dev-agent",
"description": "Marketplace for the dev-agent plugin -- an autonomous research/implement/test/review development workflow.",
"owner": {
"name": "Surjal"
},
"plugins": [
{
"name": "dev-agent",
"description": "Deep autonomous AI developer agent with architect/researcher/ux-designer/developer/frontend-developer/tester/visual-qa/reviewer subagents and /analyze, /implement, /test, /review commands. Persistent resumable execution state (.devagent/), a 15-stage lifecycle with explicit security/performance review, framework-agnostic; Playwright-based visual QA is optional and never auto-installed; enforces a verified target-project boundary at the tool layer with a fail-closed PreToolUse guard.",
"source": "./",
"category": "development"
}
]
}
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 · 17 lines scan A 4aab250d225d
dev-agent is a plugin published in the GitHub repository Surjal/dev-agent (2 stars, last pushed 17d 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
agent-inject
Inject copilot-api rules and SubagentStart agent context.
borski
Travel hacking plugins by Borski. Flights, hotels, points, miles, awards.
superset
Plugin marketplace listing 1 plugin: superset.
claude
Persistent memory for Claude Code. Capture work across sessions and recall relevant context.
claude-architect
CLI coding-agent orchestration for Claude through Codex, OpenCode, Pi, and Pythinker Code, with a commitment-boundary advisor.
3xa-harness
Discipline skills for agents doing long-running real work: freeze the scope, gate what only a human can judge, log the decisions, close out honestly.