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 ClarentCinematics/Codex-Skills-for-Enterprise --skill requirements-to-acceptance-criteriagit clone --depth 1 https://github.com/ClarentCinematics/Codex-Skills-for-EnterpriseWrote 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/clarentcinematics/codex-skills-for-enterprise/requirements-to-acceptance-criteria)<a href="https://agentmods.dev/skills/clarentcinematics/codex-skills-for-enterprise/requirements-to-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/requirements-to-acceptance-criteria/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/clarentcinematics/codex-skills-for-enterprise/requirements-to-acceptance-criteria"><img src="https://agentmods.dev/badge/skills/clarentcinematics/codex-skills-for-enterprise/requirements-to-acceptance-criteria.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.00066 | $0.00454 |
| Opus 5.5 | $0.00026 | $0.00182 |
| Sonnet 5.5 | $0.00013 | $0.00091 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
requirements-to-acceptance-criteria 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 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.
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.
What it actually says
Requirements To Acceptance Criteria
Workflow
- Identify product goal, users, problem, scope, non-goals, dependencies, owner, and launch constraints.
- Extract explicit requirements and separate them from assumptions, questions, and suggested implementation details.
- Convert requirements into testable acceptance criteria with observable behavior.
- Add test scenarios for happy path, edge cases, permissions, errors, data states, and rollout.
- Flag missing owners, dependencies, launch constraints, metrics, and unresolved assumptions.
Script-Assisted Workflow
When given a Markdown spec or PRD draft, run scripts/check_requirements_spec.py --input <path> before drafting criteria. Use --json when structured readiness evidence is needed. The helper checks for missing sections and unresolved assumptions; Codex still writes the final criteria and questions.
Output Standard
Use this structure by default:
- Requirement Summary: goal, user, scope, and readiness.
- Acceptance Criteria: numbered, testable criteria using provided facts.
- Test Scenarios: happy path, edge cases, error states, permissions, and rollout checks.
- Dependencies: systems, teams, data, designs, decisions, or approvals when stated.
- Launch Constraints: rollout, migration, support, documentation, metrics, or risk constraints.
- Open Questions: missing facts that block implementation or testing.
- Caveats: assumptions, non-inferred fields, and review needs.
Rules
- Do not invent scope, owner, launch date, metric target, design approval, or customer commitment.
- Keep criteria observable and testable.
- Separate requirements from implementation suggestions unless the source requires a specific implementation.
- Mark unsupported assumptions and unresolved questions explicitly.
References
Read references/acceptance-rubric.md when converting ambiguous requirements into acceptance criteria and test scenarios.
What ships with it
3 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.
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 · 42 lines · 66 tokens per session scan A 4a0306db3d46
requirements-to-acceptance-criteria is a skill published in the GitHub repository ClarentCinematics/Codex-Skills-for-Enterprise (2 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 454 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
secops-detection-engineering
Author, validate, test, and deploy YARA-L 2.0 detection rules and evaluate end-to-end detection coverage gaps in Google SecOps. Use when writing new detection rules, tuning existing rules, validating syntax, testing logic against historical telemetry, or evaluating detection coverage against threat intelligence blogs…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
rtvi-vlm-perf-testing
Plan, run, and diagnose reproducible RT-VLM GPU performance canaries and benchmarks. Use this skill when running fresh-container stream-capacity, semantic-isolation, latency, throughput, or regression experiments against an RTVI microservices checkout.
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.