improve

A workflow for implementing feature improvements documented in docs/improvements.md, with tests and separate commits for each feature.

In plain words
What is it for?
Use it to implement small groups of independent features one at a time or coordinate several features across an agent team.
Why use it?
It reduces the chance that useful improvements are overlooked and makes each change easier to review or undo.

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/codenamev/claude_memory/improve
Any agent
npx skills add codenamev/claude_memory --skill improve
Clone the repo
git clone --depth 1 https://github.com/codenamev/claude_memory

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,355 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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.04355
Opus 5 $0.00015 $0.02178
Sonnet 5 $0.00006 $0.00871
Haiku 4.5 $0.00003 $0.00436

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

Security

Grade A, and why

improve 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.

.claude/skills/improve/SKILL.md · 632 lines

How it starts

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

Feature Improvements - Incremental Implementation

Systematically implement feature improvements from docs/improvements.md, making tested, atomic commits for each feature addition.

Execution Modes

This skill supports two modes, passed as the first argument:

  • sub-agent (default): A single agent works through improvements sequentially. Best for small batches (1-3 features) or features with dependencies.
  • agent-team: Spawns a coordinated team of agents that implement independent features in parallel. Best for larger batches (3+) of independent features.

Mode: agent-team

When invoked with agent-team, follow this process:

Step 1: Read and Assess Improvements

Read docs/improvements.md and identify all implementable features using the same feasibility criteria as sub-agent mode (skip Categories D-F, "Features to Avoid", "If Requested" items).

Step 2: Group Independent Features

Partition implementable features into independent groups:

  • Features touching different files can be parallelized
  • Features sharing files or with dependencies must be sequential
  • Aim for 3-5 teammates maximum

Step 3: Create the Agent Team

Create an agent team. For each teammate:

  1. Assign one or two related features per teammate
  2. Provide full context — teammates don't share your conversation history
  3. Include these instructions for each teammate:
    • Read relevant existing code before making changes
    • Follow the project's code style (Standard Ruby, frozen_string_literal)
    • Write tests for all new functionality
    • Run bundle exec rake standard:fix before committing
    • Run relevant spec file after each edit, full suite before committing
    • Run bundle exec rspec to verify all tests pass
    • Make atomic commits with [Feature] prefix format
    • Update docs/improvements.md to mark features as implemented
    • Reference .claude/skills/improve/feature-patterns.md for implementation recipes

Step 4: Monitor and Coordinate

Read the full file on GitHub · 632 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 632 lines · 29 tokens per session scan A 4e9d405cb635

Subscribe to this mod's changes

improve is a skill published in the GitHub repository codenamev/claude_memory (24 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 4,355 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens