agentmods.dev

acceptance-orchestrator

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

An end-to-end workflow for taking a software task from an issue through coding, review, deployment, and acceptance checks. It treats the task as complete only when its agreed requirements are proven with evidence.

In plain words
What is it for?
Running issue-based coding tasks through defined stages, coordinating handoffs, checking acceptance criteria, and verifying a deployment.
Why use it?
It prevents work from stopping after code is changed but before review, deployment, or verification is finished. It also makes unresolved problems explicit by escalating them.

Skill for Claude Code

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

Part of the agentic-awesome-skills-claude plugin — 36 skills shipped together

not rated 281repo +8 1mo ago A scan 37 tokens copy · 100% MIT

Good fit Running issue-based coding tasks through defined stages, coordinating handoffs, checking acceptance criteria, and verifying a deployment.

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

Made for: Claude Code.

Or install agentic-awesome-skills-claude, the plugin that ships this one along with the rest of its 36 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/lingxling/awesome-skills-cn/acceptance-orchestrator/github.svg)](https://agentmods.dev/skills/lingxling/awesome-skills-cn/acceptance-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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/lingxling/awesome-skills-cn/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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 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.

ModelPer sessionOnce 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 12d ago against content hash d1824a4f2f64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 12d 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.

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

  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.

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.

  1. 12d 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 lingxling/awesome-skills-cn (281 stars, last pushed 1mo 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.

E2E testingProject managementTestingagentsanthropicawesome-listchineseclaude-skillsskills
Related

Other skills, from other repositories

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Prat011/awesome-llm-skills · 35 tokens

screen-reader-testing

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

wshobson/agents · 39 tokens

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

wshobson/agents · 51 tokens

api-tester

A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.

laolaoshiren/claude-code-skills-zh · 86 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.

code-yeongyu/oh-my-openagent · 51 tokens

smoke-test

Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…

tobihagemann/turbo · 88 tokens