Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/codex-qa
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex. The first-party method drives the real `codex app-server` against an isolated CODEX_HOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by asserting hook/started + hook/completed notifications. Also: isolated install verification, per-component hook probes, a tmux TUI smoke, and runtime log observation (RUST_LOG /
Passed 16 of 19 test cases with the skill, and 3 of 19 without it.
and 19 more in the full report
16 fixed3 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
What specific prompt injection content and trigger phrase are validated by the unit test probe for the ultrawork component?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies <ultrawork-mode> as the injected tag. | Missed | Passed |
| Identifies ulw as the trigger prompt. | Missed | Passed |
The instructions your model reads when the skill loads.
QA the omo Codex Light edition (packages/omo-codex/, shipped as lazycodex). We
exercise OUR plugin in a REAL Codex while touching nothing of the user's setup:
an isolated CODEX_HOME + a local mock model means no real API call and the real
~/.codex is never read or written. Each helper script ships a --self-test
that asserts its scenario against the live machine, so the scripts are both the
QA tools and their own regression checks.
Verified against codex-cli 0.140.0 (node, jq, tmux, bun on macOS). Confirm with
codex --version; check a flag with codex <cmd> --help.
CODEX_HOME (created by cqa_mk_isolated_home) and a LOCAL mock model
provider (cqa_start_mock). Never QA against the real ~/.codex, never hit a
real model API. The bundled scripts enforce this; if you run codex by hand,
export CODEX_HOME="$(mktemp -d)/codex"; mkdir -p "$CODEX_HOME" FIRST (a set
CODEX_HOME must already exist or codex hard-errors).~/.codex/config.toml before and after and asserts it is unchanged. If you
script by hand, do the same.codex is a shell function that injects --profile quotio.
Bash scripts bypass it and get the real binary; never rely on the interactive
alias. See references/isolation.md.hook/started / hook/completed), not log scraping. See
references/app-server.md..omo/evidence/<YYYYMMDD>-<slug>/ (no evidence file == the QA did not happen).cd <this-skill-dir> # .agents/skills/codex-qa
bash scripts/lib/common.sh --self-check # confirm deps + isolation harness
Docker is the default QA surface. Run this QA inside a disposable container
test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.