Borrowing it
Nothing to install: this file belongs to sorryorc/mcp-codex-worker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sorryorc/mcp-codex-worker/main/.claude/skills/worker-validation-and-qa/SKILL.mdgit clone --depth 1 https://github.com/sorryorc/mcp-codex-workerWrote 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/sorryorc/mcp-codex-worker/worker-validation-and-qa)<a href="https://agentmods.dev/skills/sorryorc/mcp-codex-worker/worker-validation-and-qa"><img src="https://agentmods.dev/badge/skills/sorryorc/mcp-codex-worker/worker-validation-and-qa.svg" alt="Measured on agentmods" 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.00030 | $0.00191 |
| Opus 5 | $0.00015 | $0.00096 |
| Sonnet 5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
worker-validation-and-qa 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.
What it actually says
Worker Validation And QA
Evidence Bar
- Passing checks prove only the checked behavior.
- A receipt proves runtime execution shape, not semantic correctness.
- A low trajectory score is a review signal.
- Critical tasks need independent semantic review or main-thread review.
Acceptance Checklist
- Relevant tests passed.
- Scope is clean.
- Receipt abnormal verdict is accepted or explicitly handled.
- Episode has no unexpected missing gates.
- No new blocking behavior without
blocking_policy=enforce.
When Not To Use
Do not use this for writing user-facing docs. Use worker-docs-and-writing.
Verification
npm testnpm run codex:guard
Provenance and maintenance
Add failed QA cases to tests before changing acceptance rules.
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 · 35 lines · 30 tokens per session scan A 7594f4f62890
worker-validation-and-qa is a skill published in the GitHub repository sorryorc/mcp-codex-worker (2 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 191 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-31.
Other skills, from other repositories
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
verify
Runs this project's check chain through scripts/verify.py and reads the receipt it writes. Fires when tracked changes are finished, when the user asks whether work passes, before a commit, and before reporting a task done. Stays dormant in repositories with no detectable check chain, during read-only audits, and for…
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.