AAS Core is a local control plane for coding agents that lets them search a large catalogue of skills, choose a stack, validate it, and create a reproducible plan. It is used to assemble and review agent workflows through its CLI, local MCP server, catalogue, plugins, and Workbench. The catalogue add-ons provide the skills, plugins, bundles, and workflows that AAS Core helps agents select and validate.
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.
npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestratorgit clone --depth 1 https://github.com/sickn33/agentic-awesome-skillsWrote 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.
[](https://agentmods.dev/skills/sickn33/agentic-awesome-skills/acceptance-orchestrator)<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-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.
<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/acceptance-orchestrator"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/acceptance-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00847 |
| Opus 5 | $0.00018 | $0.00424 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
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 4d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
- acceptance-orchestrator — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 123 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-gateclosed-loop-deliveryverification-before-completion
Optional supporting skills:
deploy-devpr-watchpr-review-autopilotgit-ship
Inputs
Require these inputs:
- issue id or issue body
- issue status
- acceptance criteria (DoD)
- target environment (
devdefault)
Fixed defaults:
- max iteration rounds =
2 - PR review polling =
3m -> 6m -> 10m
State Machine
intakeissue-gatedexecutingreview-loopdeploy-verifyacceptedescalated
Workflow
-
Intake
- Read issue and extract task goal + DoD.
-
Issue gate
- Use
create-issue-gatelogic. - If issue is not
readyor execution gate is notallowed, stop immediately. - Do not implement anything while issue remains
draft.
- Use
-
Execute
- Hand off to
closed-loop-deliveryfor implementation and local verification.
- Hand off to
-
Review loop
- If PR feedback is relevant, batch polling windows as:
- wait
3m - then
6m - then
10m
- wait
- After the
10mround, stop waiting and process all visible comments together.
- If PR feedback is relevant, batch polling windows as:
-
Deploy and runtime verification
- If DoD depends on runtime behavior, deploy only to
devby default. - Verify with real logs/API/Lambda behavior, not assumptions.
- If DoD depends on runtime behavior, deploy only to
-
Completion gate
- Before any claim of completion, require
verification-before-completion. - No success claim without fresh evidence.
- Before any claim of completion, require
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.
- 4d ago Changed · +6 lines 1aca0dd81517
- 11d ago First seen · 117 lines · 37 tokens per session scan A d1824a4f2f64
acceptance-orchestrator is a skill published in the GitHub repository sickn33/agentic-awesome-skills (46,230 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 847 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pr-review-expert
Professional Pr Review Expert skill. Orchestrate technical collaboration, design reviews, sprint planning, and system diagnostics.
issue
You are a senior engineering lead and product architect. Given an observation, bug, or gap, conduct a thorough multi-dimensional investigation, find the root cause, plan the resolution, and create a detailed actionable GitHub issue.
asana
Organize Asana projects and tasks, configure custom fields and rules, and automate scoped updates through its API.
build-nitro-modules
Builds React Native Nitro Modules from scratch in a monorepo. Scaffolds with Nitrogen, authors HybridObject TypeScript specs, generates native boilerplate, implements in C++/Swift/Kotlin, wires an example app, and prepares for npm publishing. Use when creating a new Nitro Module, implementing native functionality via…
revops
When the user wants help with revenue operations or the marketing-to-sales handoff — 'RevOps,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'data hygiene,' 'leads aren't getting to sales.' For prospecting, see cold-email; drip campaigns, email-sequence; pricing…
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.