What is acceptance-orchestrator?

A workflow coordinator for taking a coding issue from intake through implementation, review, deployment, and acceptance. Acceptance means checking that the stated requirements are actually met with evidence.

Use it when an issue has acceptance criteria and should proceed through coding, review, deployment, and final verification with little repeated supervision.

It prevents work from being treated as finished merely because code changed, and provides explicit escalation when the requirements cannot be verified.

acceptance-orchestrator — Skill for Claude Code by Ghosteken

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.

Any agent

npx skills add Ghosteken/agent-harness --skill acceptance-orchestrator

Clone the repo

git clone --depth 1 https://github.com/Ghosteken/agent-harness

Made for: Claude Code.

Or install agent-harness, the plugin that ships this one along with the rest of its 173 skills, 11 commands, 12 agents.

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/ghosteken/agent-harness/acceptance-orchestrator.svg)](https://agentmods.dev/skills/ghosteken/agent-harness/acceptance-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/ghosteken/agent-harness/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/acceptance-orchestrator.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 817 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 100% copy Near-identical to another mod 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.00037	$0.00817
Opus 5	$0.00018	$0.00409
Sonnet 5	$0.00007	$0.00163
Haiku 4.5	$0.00004	$0.00082

Measured 8d ago against content hash d1824a4f2f64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

acceptance-orchestrator 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 8d 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.

Origin

This is a copy

100% identical to acceptance-orchestrator — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

archive/skills-community/acceptance-orchestrator/SKILL.md · 117 lines

How it starts

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

Acceptance Orchestrator

Overview

Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.

Core rule: do not optimize for "code changed"; optimize for "DoD proven".

When to Use

The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
You need structured handoff across implementation, review, deployment, and final verification.
You want explicit stop conditions and escalation instead of silent partial completion.

Required Sub-Skills

create-issue-gate
closed-loop-delivery
verification-before-completion

Optional supporting skills:

deploy-dev
pr-watch
pr-review-autopilot
git-ship

Inputs

Require these inputs:

issue id or issue body
issue status
acceptance criteria (DoD)
target environment (dev default)

Fixed defaults:

max iteration rounds = 2
PR review polling = 3m -> 6m -> 10m

State Machine

intake
issue-gated
executing
review-loop
deploy-verify
accepted
escalated

Workflow

Intake
- Read issue and extract task goal + DoD.
Issue gate
- Use create-issue-gate logic.
- If issue is not ready or execution gate is not allowed, stop immediately.
- Do not implement anything while issue remains draft.
Execute
- Hand off to closed-loop-delivery for implementation and local verification.
Review loop
- If PR feedback is relevant, batch polling windows as:
  - wait 3m
  - then 6m
  - then 10m
- After the 10m round, stop waiting and process all visible comments together.
Deploy and runtime verification
- If DoD depends on runtime behavior, deploy only to dev by default.
- Verify with real logs/API/Lambda behavior, not assumptions.
Completion gate
- Before any claim of completion, require verification-before-completion.
- No success claim without fresh evidence.

Read the full file on GitHub · 117 lines

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.

8d ago First seen · 117 lines · 37 tokens per session scan A d1824a4f2f64

Subscribe to this mod's changes

acceptance-orchestrator is a skill published in the GitHub repository Ghosteken/agent-harness (2 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to acceptance-orchestrator, differing in 6 lines, and is treated as a copy.

Claude Code Planning Project management agent-orchestration agent-skills ai-agents automation devtools

extract-action-items

Extract a list of action items with owners and deadlines from a meeting transcript.

thesongzhu/Friday · 0 tokens

worker

Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams.

IAPro-Community/Orquestrador-Maestro · 19 tokens

factory-handoff

Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.

watt-mind/factory · 47 tokens

ticket-spec

Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.

watt-mind/factory · 45 tokens

ticket-master

Use when the user wants to keep an open triage console for a software project - capturing bugs/change-requests as structured tickets, scoring them, and routing them to the right AI provider/sub-agent for an immediate fix or into the project's task management. Cloud-ready: works across multiple machines sharing a…

ellmos-ai/ticket-master · 89 tokens

team

N coordinated agents on shared task list using tmux-based orchestration.

IAPro-Community/Orquestrador-Maestro · 15 tokens