code-review-context

A set of rules for managing the conversation history sent to a coding agent. It keeps context additions structured, limited in size, and added incrementally.

In plain words
What is it for?
Use it when designing or reviewing an agent's context system. It applies to history handling, bounded context fragments, and manual review of unusually large additions.
Why use it?
It helps prevent oversized or unstable context from making the agent slower, less consistent, or harder to review. Large new context items receive extra attention before being added.

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-context
Any agent
npx skills add Kbediako/codex-termux-pocket --skill code-review-context
Clone the repo
git clone --depth 1 https://github.com/Kbediako/codex-termux-pocket

Made for: Claude Code, Codex.

Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 142 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.00007 $0.00142
Opus 5 $0.00003 $0.00071
Sonnet 5 $0.00001 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash 0af80b6388cc, 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-context 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 yesterday.

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-context — 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-context/SKILL.md · 13 lines

What it actually says

Codex maintains a context (history of messages) that is sent to the model in inference requests.

  1. No history rewrite - the context must be built up incrementally.
  2. Avoid frequent changes to context that cause cache misses.
  3. No unbounded items - everything injected in the model context must have a bounded size and a hard cap.
  4. No items larger than 10K tokens.
  5. Highlight new individual items that can cross >1k tokens as P0. These need an additional manual review.
  6. All injected fragments must be defined as structs in core/context and implement ContextualUserFragment trait
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. yesterday First seen · 13 lines · 7 tokens per session scan A 0af80b6388cc

Subscribe to this mod's changes

code-review-context is a skill published in the GitHub repository Kbediako/codex-termux-pocket (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 142 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-context, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

android-adb-control

Direct control of Android physical devices and Termux environments via Android Debug Bridge (ADB).

AbdullahMalik17/malikclaw · 22 tokens

manage-usage-sidebar

Install, check, repair, or uninstall the native Codex Usage Sidebar companion. Use when the user asks about the Codex usage header indicator, says it disappeared after a Codex update, requests repair, status, installation, or removal, or invokes @codex-usage-sidebar.

JaceHwang/codex-usage-sidebar · 62 tokens

android-phone-control

Control an Android phone from a local Termux/Linux host using a deterministic ADB toolkit: device checks, wake/unlock/session mode, screenshots, UI dumps, taps, text input, key events, app launch, and safe app smoke tests.

patrickdass93/android-phone-control-skill · 53 tokens

seiro-mcp-visionos-build-operator

Build and diagnose visionOS projects with Seiro MCP. Use inspectxcodeschemes (if needed) -> validatesandboxpolicy -> buildvisionosapp -> inspectbuilddiagnostics (on failure) -> fetchbuildoutput (on success), and avoid direct xcodebuild or swiftc unless the user explicitly asks for shell-level execution or MCP cannot…

karad/seiro-mcp · 86 tokens

apk-smb-sync

Build a simple post-update Android APK delivery flow that reads the app version and copies a dated findeck APK into the LAN SMB share. Use when the user mentions APK update sync, Android release handoff, SMB share upload, 局域网共享, or asks to archive the latest APK by version date.

fainaltn/findeck · 67 tokens

find-release

A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects.

flutter/flutter · 67 tokens