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.
npx skills add DevOtts/parallel-lifecycle --skill parallel-lifecyclegit clone --depth 1 https://github.com/DevOtts/parallel-lifecycleWrote 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/skills/devotts/parallel-lifecycle/parallel-lifecycle)<a href="https://agentmods.dev/skills/devotts/parallel-lifecycle/parallel-lifecycle"><img src="https://agentmods.dev/badge/skills/devotts/parallel-lifecycle/parallel-lifecycle/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/skills/devotts/parallel-lifecycle/parallel-lifecycle"><img src="https://agentmods.dev/badge/skills/devotts/parallel-lifecycle/parallel-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00157 | $0.00989 |
| Opus 5.5 | $0.00063 | $0.00396 |
| Sonnet 5.5 | $0.00031 | $0.00198 |
| Haiku 4.5 | $0.00016 | $0.00099 |
Grade A, and why
parallel-lifecycle scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
until curl -sf "http://127.0.0.1:$PORT" >/dev/null; do sleep 0.5; done How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
parallel-lifecycle
Give every git worktree its own isolated, disposable runtime, so N parallel coding sessions never fight over port 3000, the database, or the browser. Everything keys off one generated contract file, .env.worktree.
Claude Code gets the full plugin: a
SessionStarthook provisions each worktree automatically and aSessionEndhook tears it down. On every other tool, this skill is the workflow and you run the provisioning script yourself (one command). The behavior is identical; only the auto-wiring differs.
0. Preflight (every session)
Confirm the worktree is provisioned:
test -f .env.worktree && cat .env.worktree || echo "NOT PROVISIONED"
If NOT PROVISIONED and you are inside a linked worktree
(git rev-parse --git-dir != --git-common-dir), provision it once:
bash worktree-bootstrap.sh # the bundled Layer 0 script
Then load the contract before any dev/test command:
set -a; source .env.worktree; set +a
.env.worktree carries APP_PORT / PORT, CDP_URL, and DATABASE_URL. Ports
are deterministic free ports, written once — never auto-incremented (that
silently points the test harness at the wrong URL).
1. Pick the browser model
| Situation | Model | What to do |
|---|---|---|
| Testing your own app | 1 (default) | Use the worktree's ephemeral Chrome on $CDP_URL. Fully parallel. |
| Must use the real logged-in / anti-detection Chrome | 3 (serialize) | Drive it through your real-Chrome flow AND wrap the run in flock /tmp/cdp-9222.lock so only one session uses it at a time. |
2. Run the app on the worktree's port
npm run dev # framework reads PORT from env
until curl -sf "http://127.0.0.1:$PORT" >/dev/null; do sleep 0.5; done
3. Drive the worktree's Chrome (not :9222)
Connect over CDP to $CDP_URL. The repo ships a Playwright helper
(connect.py) that reads the contract and returns a page. For authenticated
flows, inject a saved Playwright storageState — never the real profile.
What ships with it
4 files beside SKILL.md 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 · 87 lines · 157 tokens per session scan A 37a47d2c146b
parallel-lifecycle is a skill published in the GitHub repository DevOtts/parallel-lifecycle (3 stars, last pushed 2d ago), licensed MIT. It adds 157 tokens to every session and 989 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns.
ui-automation-workflows
Accessibility-first UI automation using IDB. Query accessibility tree (fast, 50 tokens) before screenshots (slow, 170 tokens). Use when automating simulator interactions, tapping UI elements, finding buttons, or testing user flows. Covers idb-ui-describe, idb-ui-tap, idb-ui-find-element patterns.
ccc-testing
Testing domain router: picks the lane for TDD, E2E, visual regression, load testing, QA, regression checks, evals or verification and runs test-writing work in an isolated worktree. Use when the user asks to write tests, plan a test strategy, or test, verify or load-test a change.
e2e-testing
Use when writing or maintaining end-to-end tests — Playwright (preferred) or Cypress critical-flow suites. Pattern playbook: page objects, stable selectors, fixtures and isolation, condition-based waiting, flaky quarantine, CI wiring. Backs the e2e-runner agent.
verify
Drive the real CLI (node n8n-decanter.mts ) as a subprocess against a throwaway mock n8n API — do not import lib/ modules directly.
verify-chrome-cdp-ex
Verify chrome-cdp-ex (CLI and MCP driving a real Chrome). Use when proving a fix, or when a reviewer re-runs the user path on a PR head.