Claude Code Grows Up: Hooks, Skills, and Open Models That Ship

Today's findings

1. #1 coding-posture: Task-Aware Modes for AI Coding Agentstool

   A single MIT-licensed SKILL.md forces your coding agent to pick a named mode—debug, fix, test-first, refactor, migrate, unstuck—and follow a short checklist before touching any code.

   coding-posture · SKILL.md

   Six modes force an agent to pick its posture before touching code

   Debug Understand first

   Fix Minimal change

   Test-first Red before green

   Refactor Behaviour held

   Migrate Rollback ready

   Unstuck Reset & rethink

   Each mode runs a short checklist plus universal invariants; MIT-licensed, provider-agnostic.

   Why it matters: Coding agents fail not from lack of capability but from wrong posture: writing code before understanding the problem, migrating prod without a rollback plan, or faking a green test. Explicit modes with per-mode checklists and universal invariants prevent these systematically.

   How to apply: Clone github.com/alexei-led/coding-posture and drop SKILL.md into ~/.claude/skills/ for Claude Code, or use it as a Cursor rule or system prompt prefix. It is provider-agnostic and works with any agent that reads a skills file. The skill itself tells you which mode to pick for the current task.

   agentsclaude-codepromptingworkflow

   Read more: coding-posture: task-aware modes for AI coding agents — one SKILL.md, research-backed, MIT · coding-posture: task-aware modes for AI coding agents — one SKILL.md, research-backed, MIT

2. #2 checkpoint-guard: Claude Code Hook That Blocks Fake Completionstool

   A Claude Code hook that fires on every response and refuses to let the model hand off with deferred work, vague hedges, or 'we can address that separately' non-answers.

   Tool

   Checkpoint-Guard Blocks Fake Completions

   3 patterns

   Deferred work

   Vague hedges

   Non-answers

   pass warn fail

   Triggers dozens of times daily on real work.

   Why it matters: The most common Claude Code failure mode is a clean-looking response that quietly defers the hard part. Users report it triggers dozens of times daily on real work, catching partial completions that would otherwise reach code review or production.

   How to apply: Install from github.com/platcrest/checkpoint-guard and add it to your Claude Code hooks config. It runs as a response-intercept hook and triggers only on genuine fake-completion patterns, not on real completions.

   claude-codeagentsworkflow

   Read more: I made a Claude Code hook that ensures the WHOLE task is done. No more "say the word", "separate fix", "if it ever bites", and any other fake checkpoints.

3. #3 chameleon: AST-Based Repo Convention Injector for Claude Codetool

   Parses your actual repo with the TypeScript compiler, Ruby Prism, or Python libcst and injects a concrete example from your own codebase into Claude's context before every file edit, ending convention drift.

   Claude Code Plugin

   How chameleon injects repo conventions

   1

   Parse AST

   TypeScript / Ruby / Python

   2

   Select Example

   Real pattern from codebase

   Key: uses actual code, not docs

   3

   Inject Context

   Before each file edit

   Ends convention drift by showing Claude a real example from your repo.

   Why it matters: Claude Code knows how to code in general but not how your team codes specifically. It will import the wrong HTTP wrapper, skip the base class every other service extends, or recreate a helper that already exists. chameleon fixes this without prompt engineering by learning from your actual AST, not from documentation you maintain.

   How to apply: The plugin supports TypeScript, Ruby, and Python repos. Configure it to point at your repo root; before each edit it injects one real example of the pattern plus the anti-pattern to avoid. See the r/ClaudeAI post for the repo link and setup instructions.

   claude-codeworkflowfine-tuning

   Read more: Made a Claude Code plugin that learns your repo's conventions and feeds them to the model before every edit (TS / Ruby / Python)

4. #4 agentlint: Static Analyzer for MCP Server Security Configstool

   A pip-installable CLI that statically audits MCP server configs for root filesystem access, hardcoded credentials, and missing approval gates before you wire them to an agent.

   Why it matters: MCP configs are easy to misconfigure in ways that give agents much more access than intended. A static analysis pass before deployment catches the most common mistakes—an agent with root filesystem access or a leaked API key is a serious incident waiting to happen.

   How to apply: pip install leporis-agentlint, then run it against your MCP server config files. It is a lightweight Python CLI. Review the output for filesystem scope issues, credential leaks, and destructive tools without manual approval gates before connecting any agent to that MCP server.

   mcpsecurityagents

   Read more: built a quick cli tool to audit mcp server configs for security leaks

5. #5 LodeDB: Local Drop-In Vector Store with Native MCP Servertool

   A fully local pip-installable vector database with LangChain, LlamaIndex, and mem0 adapters that reports sub-millisecond p50 query latency and a one-command MCP install for Claude Code.

   LOCAL VECTOR DB

   Sub-millisecond p50, 4-7x smaller storage

   1ms

   p50 query latency

   4-7x

   smaller storage than in-memory defaults

   17.5k

   doc corpus tested

   1 cmd

   MCP install for Claude Code

   LodeDB is a fully local, pip-installable vector database with LangChain, LlamaIndex, and mem0 adapters.

   Why it matters: Most RAG setups use cloud vector databases or slow in-memory stores. LodeDB runs on-disk at sub-millisecond p50 with 4-7x smaller storage than in-memory defaults on a 17.5k-doc corpus, and the MCP integration means coding agents can query persistent memory without custom plumbing.

   How to apply: pip install lodedb. Swap your existing LangChain or LlamaIndex vector store for the LodeDB adapter. Run lodedb mcp install --client claude to register it with Claude Code. Works fully offline, no external services needed.

   ragmcplocal-llmagents

   Read more: LodeDB: a very fast local drop-in vector store for LangChain / LlamaIndex / mem0, with an MCP server for agent memory

6. #6 GLM-5.2 Matches Claude Opus on Coding-Agent Tasks at Half the Costtip

   In a controlled 45-task terminal-bench run using the identical Claude Code harness, GLM-5.2 open weights matched Claude Opus exactly—25 of 45 each—at under half the API cost.

   Coding-Agent Benchmark

   GLM-5.2 Matches Claude Opus on Coding-Agent Tasks at Half the Cost

   vs

   GLM-5.2 (open weights)

   Claude Opus (closed)

   Tasks passed (of 45)

   25

   25

   API cost ratio

   0.5x

   1x

   GLM-5.2 (open weights) wins the row Claude Opus (closed) wins the row

   Same agent harness, same 45 tasks, binary pass/fail graded by hidden tests.

   Why it matters: This is the most rigorous open-model vs frontier-model coding-agent comparison published today: same agent, same prompts, same tools, binary pass/fail graded by hidden tests, full failure transcripts included. It validates GLM-5.2 as a real cost alternative for agentic coding workloads, not just a benchmark number.

   How to apply: GLM-5.2 is available as open weights. Before switching, read the failure transcripts in the LLMDevs post to understand which task categories each model drops. Run the same 45-task set on your own task distribution to validate the result holds for your codebase.

   agentsopen-weightsbenchmarkslocal-llm

   Read more: GLM-5.2 matched Claude Opus on 45 terminal-bench coding-agent tasks at less than half the cost (full methodology + failure transcripts inside)

7. #7 Gemma4 QAT Models Get 35-53% Decode Speedup via Multi-Token Predictiontip

   New Gemma4-26B and 31B QAT releases include MTP heads that speculatively draft extra tokens, delivering 35% and 53% real-world local decode speedups with no weight changes.

   Why it matters: Multi-token prediction lets the model draft the next N tokens in parallel and verify them against the base distribution. When drafts are accepted—which they usually are for fluent continuations—you advance multiple tokens per decode step at near-single-token cost. These are ready-to-use GGUF weights, not a research prototype.

   How to apply: Download Gemma4-26B-A4B-QAT-Uncensored-HauhauCS-Balanced-MTP or Gemma4-31B-QAT-Uncensored-HauhauCS-Balanced-MTP from the HauhauCS HuggingFace profile. Use with a llama.cpp build that supports MTP. The 26B-A4B variant is designed for systems around 24GB VRAM.

   local-llmquantizationinferenceopen-weights

   Read more: Gemma4-26B-A4B & 31B-QAT Uncensored Balanced are out with MTP (35% & 53% speed boost)! · Gemma4-26B-A4B & 31B-QAT Uncensored Balanced are out with MTP (35% & 53% speed boost)! · Gemma4-26B-A4B & 31B-QAT Uncensored Balanced are out with MTP (35% & 53% speed boost)!

8. #8 Cross-Model Code Review: Use a Second Model as the Skeptictechnique

   Across 53 review runs, sending Claude Code output to a second model for review surfaced meaningful issues 88% of the time, because different models have different blind spots.

   Code Review

   Cross-Model Code Review

   Self-Review

   • Biased toward own choices
   • Misses own blind spots

   vs

   Cross-Model Review

   • 88% meaningful-issue rate
   • Different models, different blind spots

   88% rate across 53 runs, 7 projects

   Use a second model as the skeptic to catch what the first missed.

   Why it matters: A model reviewing its own output is biased toward confirming its own choices. A second model with different training finds what the first missed. The 88% meaningful-issue rate across 7 projects is high enough that this should be a standard step before shipping agent-written patches.

   How to apply: After Claude Code produces a patch, pass the diff to a second model (Codex, a local GLM-5.2, Qwen-Coder, or similar) with a focused prompt: find bugs, bad assumptions, edge cases, and things you should not ship. Keep the roles distinct: one writes, one reviews skeptically. The models tend to miss different things.

   agentsclaude-codeworkflow

   Read more: I stopped letting Claude Code review its own work

9. #9 Gearbox: Claude Code Subagent Router with 13 Days of Real Production Datatool

   A routing layer for Claude Code that classifies each subagent delegation and sends it to the cheapest capable model tier, backed by 13 days of real usage numbers.

   Why it matters: Sending every Claude Code subagent task to Opus by default is expensive and unnecessary. Simple tasks—format a file, run a grep, write a unit test—can be handled by Haiku or Sonnet without quality loss. A routing layer that identifies task complexity before delegation changes the cost curve significantly.

   How to apply: Check the r/ClaudeAI post for the Gearbox repo link. The key design insight is classifying task type at delegation time, not after a cheaper model fails. The 13-day dataset in the post provides real calibration data for routing thresholds.

   claude-codeagentscost-optimization

   Read more: I ran my Claude Code model router for 13 days. Here are the real numbers.

10. #10 97% Prompt Cache Hit Rate Makes Production Claude Sonnet Viabletip

    A production chatbot running Claude Sonnet 4.6 on every incoming DM achieved 97% prompt cache hits by keeping all static knowledge in the system prompt prefix, collapsing per-message cost.

    Why it matters: Anthropic's prompt caching charges a fraction of full token cost for cached prefixes. At 97% hit rate, the effective cost per message drops dramatically, making high-frequency production deployments economically feasible on Sonnet.

    How to apply: Put all static domain knowledge—menus, FAQs, policies, product catalogs—into the system prompt prefix and keep it byte-identical across requests. Monitor cache hit rate in the API response headers and tune your prefix structure until you are above 90% before scaling to production volume.

    claudecost-optimizationprompting

    Read more: Running Sonnet 4.6 on every Instagram DM for a 7-location restaurant. 97% cache hit is the only reason it's affordable

11. #11 Gefen: AdamW Drop-In Optimizer with 8x Training Memory Reductionpaper

    A new open-source optimizer that is a drop-in replacement for AdamW and reduces training memory 8x, making fine-tuning larger models feasible on consumer hardware.

    Why it matters: Optimizer state is often the largest memory consumer during fine-tuning, exceeding the model weights themselves. An 8x reduction means models that previously required multi-GPU setups can potentially be fine-tuned on a single consumer GPU, opening local fine-tuning to a much wider range of hardware.

    How to apply: Paper at arxiv.org/abs/2606.13894, code at github.com/ndvbd/Gefen. Replace AdamW with Gefen in your training script. Validate on a short run first to confirm loss curves match expected behavior before committing to a full fine-tune.

    fine-tuningtrainingopen-source

    Read more: Gefen is a drop-in replacement for the AdamW optimizer, claims 8x memory reduction in training (GitHub available)

12. #12 Claude Code v2.1.191: /rewind Now Available After /cleartip

    The latest Claude Code release lets you /rewind to recover session context even after a /clear, eliminating the common pain of accidentally wiping a session mid-task.

    Claude Code v2.1.191

    /rewind Now Available After /clear

    Before

    • /clear wipes session — unrecoverable

    → New recovery command

    After

    • /rewind restores context even post-clear

    Accidental /clear no longer means lost work.

    Why it matters: Accidental /clear during a long agentic run was previously unrecoverable. Now /rewind is available even post-clear, making session management far more forgiving and removing a source of lost work in multi-hour coding sessions.

    How to apply: Update to Claude Code v2.1.191 or later. After an accidental /clear, immediately run /rewind before sending another message. See the full changelog at github.com/anthropics/claude-code/releases/tag/v2.1.191.

    claude-codeworkflow

    Read more: Claude Code 2.1.191 : /rewind after you /clear