code-review-testing

code-review-testing is a skill for Claude Code, Codex from Kbediako/codex-termux-pocket. It costs 8 tokens per session (122 once invoked), scanned A, a copy of code-review-testing, Apache-2.0.

A testing guide for changes to an AI coding agent. It prefers integration tests, which check several parts working together, in the core/suite directory.

In plain words
What is it for?
Use it when changing agent logic, deciding between integration and unit tests, or finding existing test helpers. It also outlines how to start a test Codex instance with test_codex.
Why use it?
It helps catch problems in the agent's real behavior instead of only testing isolated pieces. It also makes sure important logic changes have coverage without putting test-only code into the main program.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/kbediako/codex-termux-pocket/code-review-testing
Any agent
npx skills add Kbediako/codex-termux-pocket --skill code-review-testing
Clone the repo
git clone --depth 1 https://github.com/Kbediako/codex-termux-pocket

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.

agentmods badge for code-review-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/kbediako/codex-termux-pocket/code-review-testing.svg)](https://agentmods.dev/skills/kbediako/codex-termux-pocket/code-review-testing)
Your own site
<a href="https://agentmods.dev/skills/kbediako/codex-termux-pocket/code-review-testing"><img src="https://agentmods.dev/badge/skills/kbediako/codex-termux-pocket/code-review-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00122
Opus 5 $0.00004 $0.00061
Sonnet 5 $0.00002 $0.00024
Haiku 4.5 $0.00001 $0.00012

Measured 4d ago against content hash 7722784fda70, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review-testing 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 4d 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.

Origin

This is a copy

100% identical to code-review-testing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/skills/code-review-testing/SKILL.md · 15 lines

What it actually says

For agent changes prefer integration tests over unit tests. Integration tests are under core/suite and use test_codex to set up a test instance of codex.

Features that change the agent logic MUST add an integration test:

  • Provide a list of major logic changes and user-facing behaviors that need to be tested.

If unit tests are needed, put them in a dedicated test file (*_tests.rs). Avoid test-only functions in the main implementation.

Check whether there are existing helpers to make tests more streamlined and readable.

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.

  1. 4d ago First seen · 15 lines · 8 tokens per session scan A 7722784fda70

Subscribe to this mod's changes

code-review-testing is a skill published in the GitHub repository Kbediako/codex-termux-pocket (13 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 122 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-review-testing, differing in 0 lines, and is treated as a copy.