agentmods.dev

acceptance-orchestrator

acceptance-orchestrator is a skill for Claude Code from Subhra43/antigravity-awesome-skills. It costs 37 tokens per session (697 once invoked), scanned A, a copy of acceptance-orchestrator, MIT.

An end-to-end workflow for taking a coding task from an issue through implementation, review, deployment, and acceptance checks. An acceptance criterion is a condition that must be proven before the work is considered complete.

In plain words
What is it for?
Use it to gate an issue, coordinate implementation and review, deploy to a development environment, verify the results, and accept or escalate the task.
Why use it?
It prevents treating changed code as finished without evidence that the requested outcome works. It stops early when the issue or its completion criteria are not ready.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the antigravity-awesome-skills plugin — 54 skills shipped together

not rated 2repo 6mo ago A scan 37 tokens copy · 88% MIT

Good fit Use it to gate an issue, coordinate implementation and review, deploy to a development environment, verify the results, and accept or escalate the task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/subhra43/antigravity-awesome-skills/acceptance-orchestrator
View source ↗ Subhra43/antigravity-awesome-skills sickn33.github.io
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 Subhra43/antigravity-awesome-skills --skill acceptance-orchestrator
Clone the repo
git clone --depth 1 https://github.com/Subhra43/antigravity-awesome-skills

Made for: Claude Code.

Or install antigravity-awesome-skills, the plugin that ships this one along with the rest of its 54 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.

agentmods badge for acceptance-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/subhra43/antigravity-awesome-skills/acceptance-orchestrator/github.svg)](https://agentmods.dev/skills/subhra43/antigravity-awesome-skills/acceptance-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/subhra43/antigravity-awesome-skills/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/subhra43/antigravity-awesome-skills/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.

agentmods 80×15 button for acceptance-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/subhra43/antigravity-awesome-skills/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/subhra43/antigravity-awesome-skills/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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00697
Opus 5.5 $0.00015 $0.00279
Sonnet 5.5 $0.00007 $0.00139
Haiku 4.5 $0.00004 $0.00070

Measured 1mo ago against content hash ffb796e8860c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 — 29 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.

plugins/antigravity-awesome-skills-claude/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

  1. Intake

    • Read issue and extract task goal + DoD.

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

  3. Execute

    • Hand off to closed-loop-delivery for implementation and local verification.

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

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

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

  1. 1mo 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 Subhra43/antigravity-awesome-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 697 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to acceptance-orchestrator, differing in 29 lines, and is treated as a copy.

PlanningProject management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens