A repository procedure for coordinating several workers on one engineering task. It covers writing briefs, routing review rounds, checking combined changes, and deciding whether work may be merged.

Use it to assign work lanes, collect reviews, route follow-up rounds, and read CI results before merging changes.

It gives a team a shared process when multiple workers contribute to the same task, reducing missed handoffs and incomplete checks.

How apmantza/pi-lens configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to apmantza/pi-lens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/apmantza/pi-lens/master/.claude/skills/orchestrate/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/apmantza/pi-lens

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apmantza/pi-lens/orchestrate/github.svg)](https://agentmods.dev/skills/apmantza/pi-lens/orchestrate)

Your own site

<a href="https://agentmods.dev/skills/apmantza/pi-lens/orchestrate"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/orchestrate/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/apmantza/pi-lens/orchestrate"><img src="https://agentmods.dev/badge/skills/apmantza/pi-lens/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 213 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00060	$0.00213
Opus 5.5	$0.00024	$0.00085
Sonnet 5.5	$0.00012	$0.00043
Haiku 4.5	$0.00006	$0.00021

Measured 10d ago against content hash 14afe8dd217b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrate 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 10d 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.

.claude/skills/orchestrate/SKILL.md · 17 lines

What it actually says

Orchestrate

Pointer only. This file carries no rules; the repo contracts are the source of truth and win on any conflict.

Read docs/pi-lens-orchestration.md (the procedure: brief authoring, review intake, round routing, the fold check, the CI read), then docs/pi-lens-merge-policy.md (the per-PR loop, the merge gate, the Common mistakes table). The delegation and hand-back rules a worker obeys, and the model routing a brief follows, stay in AGENTS.md "Orchestration and delegated work"; the rules those are built on are docs/engineering-principles.md.

Changes

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.

10d ago First seen · 17 lines · 60 tokens per session scan A 14afe8dd217b

Subscribe to this mod's changes

orchestrate is a skill published in the GitHub repository apmantza/pi-lens (514 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 213 once invoked, about $0.0002 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-10-27.

Planning Project management

orchestrate next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
orchestrateapmantza/pi-lens	Skill	514	yesterday	MIT	A	60	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

pi-lens: Skill for Claude Code