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 XRenSiu/claude-code-forge --skill parallel-implementationgit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/parallel-implementation)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/parallel-implementation"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/parallel-implementation/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/xrensiu/claude-code-forge/parallel-implementation"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/parallel-implementation.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.00099 | $0.06167 |
| Opus 5.5 | $0.00040 | $0.02467 |
| Sonnet 5.5 | $0.00020 | $0.01233 |
| Haiku 4.5 | $0.00010 | $0.00617 |
Grade A, and why
parallel-implementation 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 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.
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 — 670 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Implementation
用多个 agent 的并行实现替代单 agent 的顺序执行。
实测数据:对于 15+ 个独立任务的计划,并行实现比顺序执行快 2-3x,同时通过 quality-sentinel 的持续抽查保持代码质量。
Announce at start: "I'm using the parallel-implementation skill to execute tasks in parallel with a team of implementers and quality sentinel."
前置条件: 需要启用 Agent Teams 实验性功能。 在 settings.json 中添加:
"env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }
When to Use
digraph {
rankdir=TB;
start [label="计划已就绪" shape=oval];
q1 [label="任务数量?" shape=diamond];
q2 [label="任务独立性?" shape=diamond];
q3 [label="质量要求?" shape=diamond];
single [label="executing-plans\n(单 agent 快速)" shape=box];
subagent [label="subagent-driven-development\n(单 agent 高质量)" shape=box];
parallel [label="parallel-implementation\n(本 Skill)" shape=box style=filled fillcolor=lightgreen];
start -> q1;
q1 -> single [label="< 5 个"];
q1 -> q2 [label=">= 5 个"];
q2 -> single [label="强依赖\n无法并行"];
q2 -> q3 [label="大部分\n可并行"];
q3 -> subagent [label="极高\n每任务双审查"];
q3 -> parallel [label="高\n持续抽查"];
}
vs. Other Execution Skills
| 维度 | executing-plans | subagent-driven | parallel-implementation |
|---|---|---|---|
| Agent 数量 | 1 | 1 (多子代理) | N+1 (N implementers + 1 sentinel) |
| 并行度 | 顺序 | 顺序 | 并行 |
| 质量保证 | 检查点 | 每任务双审查 | 持续抽查 |
| 速度 | 快 | 慢 | 最快 |
| 适合任务数 | < 10 | < 15 | 10-50 |
| 文件冲突管理 | 不需要 | 不需要 | 需要 |
| Token 消耗 | 低 | 高 | 最高 |
| 适合场景 | MVP/快速 | 关键功能 | 大规模并行 |
The Orchestration Protocol
┌─────────────────────────────────────────────────────────────────┐
│ PARALLEL IMPLEMENTATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Step 1: PLAN INTAKE 加载计划文档,提取任务列表 │
│ ↓ │
│ │
│ Step 2: TASK ANALYSIS 分析任务依赖,划分并行组 │
│ ↓ 分配文件所有权 │
│ │
│ Step 3: TEAM ASSEMBLY TeamCreate │
│ ↓ Spawn N implementers + 1 sentinel │
│ │
│ Step 4: PARALLEL EXEC Implementers 并行执行 │
│ ↓ Sentinel 持续抽查 │
│ ↓ Lead 协调和监控 │
│ │
│ Step 5: CONVERGENCE 所有任务完成 → 最终验证 │
│ ↓ │
│ │
│ Step 6: CLEANUP Shutdown Team → 输出实现报告 │
│ │
└─────────────────────────────────────────────────────────────────┘
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 · 670 lines · 99 tokens per session scan A 6e1a9e765432
parallel-implementation is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 99 tokens to every session and 6,167 once invoked, about $0.0004 per session on Opus 5.5. 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…