A code-change review tool that looks for bugs, regressions, missing tests and violations of project guidelines. It examines staged, unstaged and related untracked files.

Use it before merging changes to inspect correctness, error handling, compatibility, unused code, test coverage and adherence to project rules.

It gives a structured review of the actual changes and their surrounding code instead of relying only on a patch. It also checks repository conventions and recent project context.

review — Skill by mochow13

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/mochow13/keen-code/review

Any agent

npx skills add mochow13/keen-code --skill review

Clone the repo

git clone --depth 1 https://github.com/mochow13/keen-code

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 661 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.00661
Opus 5	$0.00010	$0.00331
Sonnet 5	$0.00004	$0.00132
Haiku 4.5	$0.00002	$0.00066

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

Security

Grade A, and why

review 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 2d 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.

internal/skills/bundled/review/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Skill

Review focus (optional): $ARGUMENTS

Steps

Gather change context. Run in parallel:
- git status --short
- git diff --staged
- git diff
- git ls-files --others --exclude-standard
- git log -n 3 --oneline
Review both staged and unstaged changes. Treat untracked files as relevant when they appear related to the user's request, and open them directly because git diff will not show their contents.
Read project conventions. If AGENTS.md, CLAUDE.md, or CONTRIBUTING.md exist at the repo root, read them before judging the diff.
Inspect the changed code. Open the files and surrounding code needed to verify behavior. Do not rely only on the diff when control flow, data shape, or tests depend on nearby context.
Review against these checks:

Correctness
- No behavior regressions, missed edge cases, or undefined references
- Error handling matches the risk and existing project patterns
- Public contracts, CLI behavior, file formats, and compatibility are preserved unless the user asked to change them
- Imports, variables, or functions made unused by the changes are removed
Surgical Changes
- Every changed line traces to the user's request
- No "improvements" to adjacent code, comments, or formatting
- No refactored code that wasn't broken
- No deleted pre-existing dead code unless explicitly asked
Simplicity
- No speculative features or abstractions
- No unnecessary configurability
- No error handling for impossible scenarios
- Functions are as short as they can be while remaining clear
Testing
- Critical paths have tests
- New functionality is exercised by tests
- Existing tests still cover the changed behavior
- Relevant tests pass, or any unrun tests are called out with the reason
Style
- Matches existing naming and patterns
- Minimal comments (only when strictly necessary)
- Language-specific formatting applied (e.g., gofmt)

Read the full file on GitHub · 88 lines

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.

2d ago First seen · 88 lines · 21 tokens per session scan A 05cf61454f15

Subscribe to this mod's changes

review is a skill published in the GitHub repository mochow13/keen-code (60 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 661 once invoked, about $0.0001 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-30.

Code review Testing agentic-ai ai-agent ai-assistant ai-coding-agent ai-coding-tool coding-assistant

tlamatini-self-update-inclusion

Sweep the whole codebase and keep the SELF-UPDATE pipeline complete — so every new asset/feature added to Tlamatini is actually carried into a release by build.py AND survives (or is correctly replaced by) the self-update swap. Invoke whenever you add/rename a new agent, top-level file or directory, dependency…

XAIHT/Tlamatini · 171 tokens

tlamatini-daily-chat-test

Run the daily automated Tlamatini chat regression — drive a visible Chrome via Playwright, log into agentpage.html, ask up to 1000 curated safe questions one-by-one (Multi-Turn ON, ACPX/Ask-Execs/Exec-Report/Internet OFF), wait for and qualify each answer (heuristic + LLM judge on failures), then write a dated report…

XAIHT/Tlamatini · 125 tokens

tlamatini-self-modify-inclusion

Sweep the whole codebase and keep the SELF-MODIFY source snapshot complete — so the TlamatiniSourceCode/ tree that a --self-modify build ships carries every source/build asset Tlamatini needs to read, modify, and REBUILD herself, with heavy media/secrets correctly omitted+redacted and omitted binaries listed in the…

XAIHT/Tlamatini · 183 tokens

adding-external-mcp

The authoritative reference for adding a NEW external MCP server to Tlamatini universal MCP client layer. Covers the full lifecycle: catalog import, transport selection, activation, runtime provisioning, diagnosis, verification, and troubleshooting. READ THIS BEFORE calling externalmcpimport, before editing…

XAIHT/Tlamatini · 71 tokens

setup-new-acpx-key

Configure the API key (or other credential) for a registered ACPX agentid (claude/codex/cursor/gemini/qwen/copilot/pi/droid/iflow/kilocode/kimi/kiro/opencode/tlamatini) end-to-end across data.keys, config.json (top-level + acpx.agents. .env), regensecrets.py, and verification via acpdoctor.

XAIHT/Tlamatini · 92 tokens

tlamatini-agent-naming

The authoritative Tlamatini agent NAMING CONVENTION — invoke before adding, renaming, casing, displaying, or auditing any workflow agent (STM32er, Node Manager, ACPXer, Kalier, ...). Use whenever you touch agentDescription, a pool/agent directory, a CSS .canvas-item class, a JS connection handler…

XAIHT/Tlamatini · 120 tokens