Borrowing it
Nothing to install: this file belongs to Kbediako/codex-termux-pocket. 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/Kbediako/codex-termux-pocket/main/.codex/skills/code-review-change-size/SKILL.mdgit clone --depth 1 https://github.com/Kbediako/codex-termux-pocketWrote 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/kbediako/codex-termux-pocket/code-review-change-size)<a href="https://agentmods.dev/skills/kbediako/codex-termux-pocket/code-review-change-size"><img src="https://agentmods.dev/badge/skills/kbediako/codex-termux-pocket/code-review-change-size/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/kbediako/codex-termux-pocket/code-review-change-size"><img src="https://agentmods.dev/badge/skills/kbediako/codex-termux-pocket/code-review-change-size.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.00012 | $0.00091 |
| Opus 5 | $0.00006 | $0.00046 |
| Sonnet 5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
code-review-change-size 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 8d 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.
This is a copy
100% identical to code-review-change-size — 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.
What it actually says
Unless the change is mechanical the total number of changed lines should not exceed 800 lines. For complex logic changes the size should be under 500 lines.
If the change is larger, explain whether it can be split into reviewable stages and identify the smallest coherent stage to land first. Base the staging suggestion on the actual diff, dependencies, and affected call sites.
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.
- 8d ago First seen · 12 lines · 12 tokens per session scan A e8184218e0f0
code-review-change-size is a skill published in the GitHub repository Kbediako/codex-termux-pocket (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 91 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-review-change-size, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
checking-code-quality
Checks code quality metrics including complexity, duplication, naming conventions, and function length. Use when running quality gates, reviewing code smells, or checking lint rules. Automatically triggered on complex modules or post-refactor.
verifying-modules
Scans directory structure, detects missing documentation, and verifies code-doc synchronization. Use when checking module completeness, README presence, or DESIGN.md alignment. Automatically triggered after creating new modules.
aios-codemap-ops
Quick reference for code-review-graph (CRG) MCP tools. Use when you need to look up a CRG tool name, parameter, or pattern. For workflow guidance, see AGENTS.md decision checkpoints. Requires aios internal codemap install.
aios-codemap-ops
Quick reference for code-review-graph (CRG) MCP tools. Use when you need to look up a CRG tool name, parameter, or pattern. For workflow guidance, see AGENTS.md decision checkpoints. Requires aios internal codemap install.