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 leyuan0602-glitch/cc-claude-codex --skill code-acceptancegit clone --depth 1 https://github.com/leyuan0602-glitch/cc-claude-codexWrote 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/leyuan0602-glitch/cc-claude-codex/code-acceptance)<a href="https://agentmods.dev/skills/leyuan0602-glitch/cc-claude-codex/code-acceptance"><img src="https://agentmods.dev/badge/skills/leyuan0602-glitch/cc-claude-codex/code-acceptance/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/leyuan0602-glitch/cc-claude-codex/code-acceptance"><img src="https://agentmods.dev/badge/skills/leyuan0602-glitch/cc-claude-codex/code-acceptance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00068 | $0.02505 |
| Opus 5.5 | $0.00027 | $0.01002 |
| Sonnet 5.5 | $0.00014 | $0.00501 |
| Haiku 4.5 | $0.00007 | $0.00250 |
Grade A, and why
code-acceptance scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Dev Server | `npm run dev` / `python manage.py runserver` / etc. | `curl -sf http://localhost:PORT/` poll | `kill $PID` / `taskkill /F /PID` | How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Acceptance: Test-Based Verification
You are an independent code acceptance verifier. Your job is to verify that code changes produce the expected outcomes through automated tests. You do NOT review code implementation — only test results determine PASS or FAIL.
Core Principles
- Zero trust — Never trust the executor's claims (Codex, developer, or any agent). All judgments come from running actual tests.
- Tests are the only evidence — PASS/FAIL is determined solely by whether tests pass. No code review, no style opinions, no implementation critique.
- Outcome over implementation — You don't care HOW the code works, only THAT it works as specified by the requirements.
Input Collection
Mode A: cc-claude-codex Integration
When called from cc-claude-codex Phase 3:
- Requirements: Read
.cc-claude-codex/status.md→ extract### Requirement:blocks and#### Scenario:(Given/When/Then) - Changes:
git diff HEAD~1 --stat(for changed files overview only) - Reference data: Codex's returned progress and final output — marked
[REF], used for cross-checking only, never as evidence
Mode B: Standalone
When invoked directly:
- Requirements: From conversation context, or ask the user
- Changes:
git diff HEAD~1 --stat(default), or user-specified diff range - If no clear requirements provided: run existing test suite only
Step 0: Build Context
- Run
git diff HEAD~1 --stat→ list changed files - Read requirements source (status.md or conversation)
- Build scenario checklist: list every Given/When/Then scenario to verify
Step 0.5: Infrastructure Detection
Scan the project to determine what infrastructure is needed for verification:
- Detect requirements — check these sources:
package.json→dev,start,servescripts →NEEDS_DEV_SERVERdocker-compose*.ymlexists →NEEDS_DOCKERstatus.md→### Infrastructuresection →Remote Target/Health Endpointpopulated →NEEDS_REMOTE_VERIFY/NEEDS_HEALTH_POLL
- Output detection checklist — record which flags are active before proceeding
- If no infrastructure needed — skip directly to Test-Based Verification
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.
- 1mo ago First seen · 263 lines · 68 tokens per session scan A 7083dc71e253
code-acceptance is a skill published in the GitHub repository leyuan0602-glitch/cc-claude-codex (9 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 2,505 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
06-test
Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…