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 DevOtts/parallel-lifecyclenpx agentmods add plugins/devotts/parallel-lifecycle/marketplacegit clone --depth 1 https://github.com/DevOtts/parallel-lifecycleGrade A, and why
parallel-lifecycle 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://json.schemastore.org/claude-code-marketplace.json",
"name": "parallel-lifecycle",
"owner": {
"name": "DevOtts",
"url": "https://github.com/DevOtts"
},
"description": "Direct-discovery marketplace for the parallel-lifecycle plugin. Add this repo to install the plugin by itself; it is also published in the wider DevOtts marketplace.",
"plugins": [
{
"name": "parallel-lifecycle",
"source": "./plugins/parallel-lifecycle",
"version": "0.1.0",
"description": "Per-worktree isolated, disposable dev environments (app port, ephemeral Chrome/CDP, per-worktree database) behind a single .env.worktree contract, for running N parallel agentic coding sessions without collisions.",
"author": {
"name": "DevOtts",
"url": "https://github.com/DevOtts"
},
"homepage": "https://github.com/DevOtts/parallel-lifecycle",
"license": "MIT",
"keywords": [
"git-worktree",
"parallel",
"isolation",
"cdp",
"playwright",
"testing"
]
}
]
}
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 · 32 lines scan A e6f23854d8ac
parallel-lifecycle is a plugin published in the GitHub repository DevOtts/parallel-lifecycle (3 stars, last pushed 1mo 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
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
OpenOutreach
The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.
junior-flow
Helps junior developers create technical story markdown from a story tracker.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
tandem
A shared Chrome browser (human + Claude, CDP + Playwright MCP) that learns how each site is navigated: the human drives with the mouse and clears captchas/logins, Claude operates over CDP, and tandem:map persists per-site navigation memory (durable locators, drift, auto-injection).
context-optimization
Techniques for extending effective context capacity through compaction, observation masking, KV-cache optimization, and context partitioning. Double or triple effective context without larger models.