What is acceptance-orchestrator?

A workflow that drives a coding task from an issue and its acceptance criteria through implementation, review, deployment, and final verification. Acceptance criteria are the conditions that prove the work is complete.

Use it for end-to-end delivery of an issue, including review loops, deployment to a target environment, acceptance checks, and structured handoffs.

It prevents stopping after code changes alone and requires evidence that the requested result works, with explicit escalation when it cannot be verified.

acceptance-orchestrator — Skill for Claude Code and Codex by henryalou

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 henryalouf/ruflow --skill acceptance-orchestrator

Clone the repo

git clone --depth 1 https://github.com/henryalouf/ruflow

Made for: Claude Code, Codex.

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/henryalouf/ruflow/acceptance-orchestrator/github.svg)](https://agentmods.dev/skills/henryalouf/ruflow/acceptance-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/henryalouf/ruflow/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/acceptance-orchestrator/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/henryalouf/ruflow/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/acceptance-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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 757 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 91% 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.00757
Opus 5	$0.00018	$0.00378
Sonnet 5	$0.00007	$0.00151
Haiku 4.5	$0.00004	$0.00076

Measured 9d ago against content hash f821fd34e28f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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

91% identical to acceptance-orchestrator — 12 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.

.agents/skills/acceptance-orchestrator/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 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 · 113 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.

9d ago First seen · 113 lines · 37 tokens per session scan A f821fd34e28f

Subscribe to this mod's changes

acceptance-orchestrator is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 757 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to acceptance-orchestrator, differing in 12 lines, and is treated as a copy.

Planning Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

acceptance-orchestrator