What is acceptance-orchestrator?

A workflow manager for taking a coding task from an issue through implementation, review, deployment, and acceptance checks. Acceptance means confirming that the agreed requirements are actually met.

It helps extract requirements, enforce an issue-readiness check, coordinate implementation and review, deploy to a development environment, and verify the result.

It keeps work from being treated as finished just because code changed, and stops tasks that are not ready to start.

acceptance-orchestrator — Skill for Claude Code by satnamrsm

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 satnamrsm/https-github.com-sickn33-antigravity-awesome-skills --skill acceptance-orchestrator

Clone the repo

git clone --depth 1 https://github.com/satnamrsm/https-github.com-sickn33-antigravity-awesome-skills

Made for: Claude Code.

Or install antigravity-awesome-skills, the plugin that ships this one along with the rest of its 198 skills.

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/satnamrsm/https-github.com-sickn33-antigravity-awesome-skills/acceptance-orchestrator.svg)](https://agentmods.dev/skills/satnamrsm/https-github.com-sickn33-antigravity-awesome-skills/acceptance-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/satnamrsm/https-github.com-sickn33-antigravity-awesome-skills/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/satnamrsm/https-github.com-sickn33-antigravity-awesome-skills/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 697 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 88% 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.00697
Opus 5	$0.00018	$0.00349
Sonnet 5	$0.00007	$0.00139
Haiku 4.5	$0.00004	$0.00070

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

88% identical to acceptance-orchestrator — 10 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.

skills/acceptance-orchestrator/SKILL.md · 107 lines

How it starts

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

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.

Stop Conditions

Move to accepted only when every acceptance criterion has matching evidence.

Move to escalated when any of these happen:

DoD still fails after 2 full rounds
missing secrets/permissions/external dependency blocks progress
task needs production action or destructive operation approval
review instructions conflict and cannot both be satisfied

Read the full file on GitHub · 107 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.

7d ago First seen · 107 lines · 37 tokens per session scan A ffb796e8860c

Subscribe to this mod's changes

acceptance-orchestrator is a skill published in the GitHub repository satnamrsm/https-github.com-sickn33-antigravity-awesome-skills (5 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 697 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to acceptance-orchestrator, differing in 10 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