What is acceptance-orchestrator?

An end-to-end process for taking a coding task from a GitHub issue to verified completion. It checks whether the issue is ready, guides implementation and review, deploys the result, and verifies the acceptance requirements.

Use it to coordinate issue intake, implementation, pull-request review, deployment, and acceptance checks with limited manual intervention.

It prevents work from being treated as finished just because code was changed. The task remains open until its required outcome has evidence behind it, or is explicitly escalated.

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

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 ggg123124/vrchat-assistant --skill acceptance-orchestrator

Clone the repo

git clone --depth 1 https://github.com/ggg123124/vrchat-assistant

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

Your own site

<a href="https://agentmods.dev/skills/ggg123124/vrchat-assistant/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/ggg123124/vrchat-assistant/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/ggg123124/vrchat-assistant/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/ggg123124/vrchat-assistant/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 716 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 86% 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.00716
Opus 5	$0.00018	$0.00358
Sonnet 5	$0.00007	$0.00143
Haiku 4.5	$0.00004	$0.00072

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

86% identical to acceptance-orchestrator — 19 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 · 110 lines

How it starts

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

6d ago First seen · 110 lines · 37 tokens per session scan A 790c3adf29f7

Subscribe to this mod's changes

acceptance-orchestrator is a skill published in the GitHub repository ggg123124/vrchat-assistant (21 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 716 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to acceptance-orchestrator, differing in 19 lines, and is treated as a copy.

Planning Project management friends hermes hermes-agent mcp monitoring otp

github-issue-pr-attribs

Standardize GitHub ISSUE and PR metadata (Assignee, Reviewer, Labels, Project, Milestone, Development, Relationship) and ship a strong, well-structured code-review template. Includes ready-to-use issue forms, PR template, and a severity/rubric review model.

pedroiff0/awesome-skills · 64 tokens

handoff-resume

Resume in-progress coding work across sessions from a HANDOFF.md and a dirty git working tree. Use when a task says "continue from HANDOFF.md", "retomar o processamento", or when picking up a repo mid-change with uncommitted edits and an open PR. Covers reading continuity docs, reconciling the real tree, decoding repo…

pedroiff0/awesome-skills · 95 tokens

acceptance-orchestrator