agentmods.dev

orch

A coordinator for taking a Linear or GitHub work item from preparation through code changes, review, quality checks, and merging. Linear is a tool for tracking development tasks.

In plain words
What is it for?
Use it when orchestrating a repository task from an issue through implementation, review, pull-request submission, and merge.
Why use it?
It divides the work among specialist agents and sets review and fix limits so implementation can move toward a merged change.

Skill for Claude CodeCodex

65 changed today A scan 23 tokens original MIT
View the source file vanillagreencom/kendex
Install

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.

agentmods
npx agentmods add skills/vanillagreencom/kendex/orch
Any agent
npx skills add vanillagreencom/kendex --skill orch
Clone the repo
git clone --depth 1 https://github.com/vanillagreencom/kendex

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.05065
Opus 5 $0.00012 $0.02533
Sonnet 5 $0.00005 $0.01013
Haiku 4.5 $0.00002 $0.00507

Measured today against content hash 7a24bb71babb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

orch 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 today.

The scan reads SKILL.md. This mod also ships 26 executable files (scripts/lib/branch-growth.sh, scripts/lib/gh-auth.sh, scripts/lib/kendex-env.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/orch/SKILL.md · 234 lines

How it starts

The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestration

Problem with this skill? Run kendex report — it files to the owning repo automatically. Do not hand-file.

Load github and worktree before anything else; a Linear work item also needs linear. The dev and reviewer skills call orch scripts.

MODE SWITCH: you are the orchestrator. Delegate every implementation, review, and QA task to a specialist sub-agent. Never edit code unless the user explicitly asks.

The Cycle

Get the issue → dev implements → review → dev fixes blockers → re-review → push PR → review gate → shepherd to merge.

  • Bounded loops. A fix round addresses blockers only; re-review narrows to the fix diff and the domains it touched; two consecutive rounds with no new blocker end the review.
  • No edge-case churn. A finding that cannot affect real usage is declined with a one-line reason — not fixed, not filed.
  • Review must converge, by references/finding-disposition.md:
    • Every finding runs its § Decision flow, Step 0 first, and ends as one of the reply forms that section sets out.
    • A defect class recurring across rounds → its § Recurrence, never patched per comment, for a rule restated in prose or a table as much as for code.
    • A defect in code the issue's Done-when does not need, or a PR past its size tripwire → a cut, not a fix round. A round whose only findings are scope or wording asks ends the review: reply, resolve, push nothing, merge through the gate. Never --admin.
  • Ask the user only about product or experience. Scope expansion beyond the issue and revisiting a recorded decision always ask, whatever ORCH_DECISION_MODE says. Merge asks unless ORCH_MERGE_AUTONOMY=auto, which merges without asking only when every merge gate is green.
  • Acceptance is artifact-based. A round closes on a validated on-disk artifact plus git/tracker state, never on a return message.

Read the full file on GitHub · 234 lines

Files

What ships with it

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

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.

  1. today Changed · -21 lines scan C → A 7a24bb71babb
  2. 3d ago First seen · 255 lines · 23 tokens per session scan C 44ef41954028

Subscribe to this mod's changes

orch is a skill published in the GitHub repository vanillagreencom/kendex (65 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 5,065 once invoked, about $0.0001 per session on Opus 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-30.

Git and workflowProject managementagent-managementagent-managerai-agentsautomationpi-coding-agentpi-extensionpi-package
Related

Other skills, from other repositories

surf

Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.

w-winter/dot314 · 60 tokens

prose-review

Review prose written for others -- user-facing docs, prompts for other LLMs, inline comments, docstrings, and other-facing messages -- for local jargon leakage, orphaned references, missing grounding, and audience or genre misfit.

w-winter/dot314 · 50 tokens

text-search

Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.

w-winter/dot314 · 22 tokens

repoprompt-tool-guidance-refresh

Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…

w-winter/dot314 · 115 tokens

xcodebuildmcp

Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.

w-winter/dot314 · 56 tokens

agent-browser

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

w-winter/dot314 · 51 tokens