What is acceptance_test?

A pre-shipping acceptance-check rule that verifies whether automatic confirmation is enabled before asking the user to test the result.

Use it before shipping completed work to choose between skipping the acceptance checklist and asking the user to run tests and verify the result.

It prevents the workflow from asking for unnecessary approval when both auto-confirmation and acceptance are enabled, while retaining the normal test request otherwise.

acceptance_test — Skill for Claude Code and Codex by adamwang99

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 adamwang99/NEUTRON-EVO-OS --skill acceptance_test

Clone the repo

git clone --depth 1 https://github.com/adamwang99/NEUTRON-EVO-OS

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/adamwang99/neutron-evo-os/acceptance_test/github.svg)](https://agentmods.dev/skills/adamwang99/neutron-evo-os/acceptance_test)

Your own site

<a href="https://agentmods.dev/skills/adamwang99/neutron-evo-os/acceptance_test"><img src="https://agentmods.dev/badge/skills/adamwang99/neutron-evo-os/acceptance_test/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/adamwang99/neutron-evo-os/acceptance_test"><img src="https://agentmods.dev/badge/skills/adamwang99/neutron-evo-os/acceptance_test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 844 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 original No closer match found 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.00003	$0.00844
Opus 5	$0.00002	$0.00422
Sonnet 5	$0.00001	$0.00169
Haiku 4.5	$0.00000	$0.00084

Measured 10d ago against content hash bcb2e2f98466, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

acceptance_test 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 10d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (logic/__init__.py, validation/__init__.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/core/acceptance_test/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🚨 CRITICAL — Auto-Confirm Enforcement (MANDATORY, NOT OPTIONAL)

This rule is ABSOLUTE. Violating it = system failure. There are no exceptions.

How to check (EXACT steps, in order):

STEP 1: Read the file memory/.auto_confirm.json

STEP 2: Decision tree:

IF memory/.auto_confirm.json does NOT exist → go to normal acceptance test below
IF memory/.auto_confirm.json exists AND {"enabled": true} AND {"acceptance": true}:
    ✅ AUTO-CONFIRM ACTIVE → SKIP EVERYTHING BELOW
    ✅ Output: "[AUTO-CONFIRM] Acceptance test SKIPPED — auto-confirm is active. Proceeding to /ship."
    ✅ Log: acceptance auto-passed in memory
    ✅ Proceed directly to /ship
    ✅ Do NOT ask user to run any tests. Do NOT ask "does it work for you?".

IF auto-confirm is NOT active:
    → Follow normal acceptance test below (ask user to run tests)

What "SKIP" means:

❌ Do NOT ask user to run any test command
❌ Do NOT ask "does it work for you?"
❌ Do NOT present acceptance criteria checklist
❌ Do NOT wait for user verification
✅ Proceed immediately to /ship

Acceptance Test Skill — Verify Before Ship

Purpose

Before shipping, the USER must verify that what was built actually solves their problem. This is not unit testing — it's USER testing. The user runs the app and confirms it works.

Philosophy

The AI can write tests. Only the USER can pass acceptance.

Unit tests: AI writes, CI runs → tells you if code works
Acceptance tests: USER runs, USER decides → tells you if the RIGHT thing was built

When to Call

After /build step (workflow), before /ship step. The SPEC.md must have a "USER REVIEW" section with specific acceptance criteria.

Workflow

/spec (write SPEC) → USER REVIEW (user approves SPEC) → /build → /acceptance_test → /ship

Acceptance Test Flow

Step 1 — Load Acceptance Criteria from SPEC.md

Read SPEC.md. Extract all acceptance criteria marked for USER verification. If no criteria defined → ERROR: cannot run acceptance test without measurable criteria.

Read the full file on GitHub · 104 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

10d ago First seen · 104 lines · 3 tokens per session scan A bcb2e2f98466

Subscribe to this mod's changes

acceptance_test is a skill published in the GitHub repository adamwang99/NEUTRON-EVO-OS (20 stars, last pushed 4mo ago), licensed MIT. It adds 3 tokens to every session and 844 once invoked, about $0.0000 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.

Testing ai-evolution context-os integral-intelligence memory-2-0 meritocracy neutron-evo

acceptance_test