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 agentmods add skills/ezotoff/ez-omo-config/parallel-devnpx skills add EZotoff/ez-omo-config --skill parallel-devgit clone --depth 1 https://github.com/EZotoff/ez-omo-configWrote 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/ezotoff/ez-omo-config/parallel-dev)<a href="https://agentmods.dev/skills/ezotoff/ez-omo-config/parallel-dev"><img src="https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/parallel-dev.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01861 |
| Opus 5 | $0.00000 | $0.00931 |
| Sonnet 5 | $0.00000 | $0.00372 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
parallel-dev 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
parallel-dev
Should I Parallelize? Decision Framework
BEFORE spawning worktrees, evaluate:
MANDATORY Preconditions (ALL must be YES)
- Can the work be split into 2+ INDEPENDENT subtasks? (no shared state, no sequential dependencies)
- Will each subtask touch DIFFERENT files? (minimal overlap = minimal merge conflicts)
- Is the total effort > 30 minutes? (parallelization overhead: ~5 min setup + ~5 min merge per agent)
Risk Assessment (proceed if acceptable)
- If one agent fails, can others continue? (failure isolation)
- Can merge conflicts be resolved? (same-file changes = high conflict risk)
Decision Matrix
| Subtasks | File Overlap | Effort | Decision |
|---|---|---|---|
| 1 | N/A | Any | ❌ NO — not parallelizable |
| 2+ | None | <30min | ❌ NO — overhead exceeds benefit |
| 2+ | None | >30min | ✅ YES — parallelize |
| 2+ | Some | >30min | ⚠️ CAUTION — plan for conflicts |
| 2+ | High | Any | ❌ NO — sequential is safer |
Examples
- ✅ "Implement auth + Implement payments" → Different modules, parallelize
- ✅ "Fix bug in API + Add tests for utils" → Different files, parallelize
- ❌ "Refactor X + Add feature using X" → Sequential dependency, sequential execution
- ❌ "Fix typo + Update README" | <5min total → Overhead exceeds benefit, sequential
- ⚠️ "Update header in app.tsx + Add route in app.tsx" → Same file, sequential or plan for conflict
Header
- Name:
parallel-dev - Description: Coordinate multi-agent parallel development with isolated worktrees, state-driven monitoring, and safe merge handoff
- Triggers:
/parallel-dev,parallel development,spawn agents
Workflow Overview
Decision Framework
→ Pre-Flight Check
→ Spawn Worktrees
→ Dispatch Tasks
→ Monitor Progress
→ Trigger Merge
→ Cleanup/Close
Lifecycle: Decision → Spawn worktrees → Dispatch tasks → Monitor → Merge → Cleanup.
What ships with it
1 file 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.
- 4d ago First seen · 275 lines · 0 tokens per session scan A 05f737f34e2c
parallel-dev is a skill published in the GitHub repository EZotoff/ez-omo-config (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,861 tokens. 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 skills, from other repositories
fusion-setup
Use when a user wants to set up, configure, install, or reconfigure the opencode Fusion agent team - a strong main/build agent that plans and reviews but cannot edit files, delegating all edits to a cheaper sidekick subagent, plus an explore search agent and optional research/design/reviewer/vision specialists.…
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.