What is improve-codebase-architecture?

A codebase architecture review that looks for modules whose responsibilities or interfaces make future changes harder, then presents possible refactors in an HTML report.

Use it to inspect recently changed or troublesome parts of a codebase, compare architectural improvement options, and examine a selected option in more detail.

It helps reveal structural friction before it grows into repeated maintenance work. The suggested refactors are reviewed further only after you choose one.

improve-codebase-architecture — Skill by kwaa/skills

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.

Any agent

npx skills add kwaa/skills --skill improve-codebase-architecture

Clone the repo

git clone --depth 1 https://github.com/kwaa/skills

Made for: Claude Code, Codex.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/kwaa/skills/improve-codebase-architecture/github.svg)](https://agentmods.dev/skills/kwaa/skills/improve-codebase-architecture)

Your own site

<a href="https://agentmods.dev/skills/kwaa/skills/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/kwaa/skills/improve-codebase-architecture/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kwaa/skills/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/kwaa/skills/improve-codebase-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 95% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.01349
Opus 5.5	$0.00013	$0.00540
Sonnet 5.5	$0.00006	$0.00270
Haiku 4.5	$0.00003	$0.00135

Measured 10d ago against content hash 552240a5ab5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

improve-codebase-architecture 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 10d 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.

Origin

This is a copy

95% identical to improve-codebase-architecture — 2 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.

.agents/skills/improve-codebase-architecture/SKILL.md · 72 lines

How it starts

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

Improve Codebase Architecture

Surface architectural friction and propose deepening opportunities: refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.

This command is informed by the project's domain model and built on a shared design vocabulary:

Call the Skill tool with "codebase-design" for the architecture vocabulary (module, interface, depth, seam, adapter, leverage, locality) and its principles (the deletion test, "the interface is the test surface", "one adapter = hypothetical seam, two = real"). Use these terms exactly in every suggestion, and don't drift into "component," "service," "API," or "boundary."
The domain language in GLOSSARY.md gives names to good seams; ADRs in docs/adr/ record decisions this command should not re-litigate.

Process

1. Explore

Scope before you scan: YAGNI. Deepening a module pays off by making future changes to it easier, so put extra weight on the parts of the codebase that have recently changed. Decide where to look before you look:

If the user named a direction (a module, a subsystem, a pain point), take it, and skip the inference below.
Otherwise, walk back a good stretch of the commit history (git log --oneline) to find the codebase's hot spots, the files and areas that keep coming up, and let those paths pull your attention first. If the changes are scattered with no clear hot spot, widen the net.

Read the project's domain glossary (GLOSSARY.md) and any ADRs in the area you're touching first.

Then spawn a sub-agent to walk the codebase. Don't follow rigid heuristics; explore organically and note where you experience friction:

Where does understanding one concept require bouncing between many small modules?
Where are modules shallow, with an interface nearly as complex as the implementation?
Where have pure functions been extracted just for testability, but the real bugs hide in how they're called (no locality)?
Where do tightly-coupled modules leak across their seams?
Which parts of the codebase are untested, or hard to test through their current interface?

Read the full file on GitHub · 72 lines

Files

What ships with it

2 files 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.

10d ago First seen · 72 lines · 32 tokens per session scan A 552240a5ab5c

Subscribe to this mod's changes

improve-codebase-architecture is a skill published in the GitHub repository kwaa/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 1,349 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to improve-codebase-architecture, differing in 2 lines, and is treated as a copy.

Code review Planning agent-skills skills

improve-codebase-architecture next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
improve-codebase-architecturekwaa/skills	Skill	2	11d ago	MIT	A	32	Claude Code, Codex
agent-watchdogBuilderIO/skills	Skill	4.6k	5d ago	MIT	A	115	Claude Code, Codex
comet-verifyrpamis/comet	Skill	3.3k	yesterday	MIT	A	32	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	6d ago	MIT	A	115	Claude Code, Codex
no-commentsbacknotprop/pstack	Skill	3.8k	yesterday	MIT	A	20	Claude Code, Cursor
graphify-dotnetmanagedcode/dotnet-skills	Skill	509	today	MIT	A	125	Claude Code, Codex
pr-description-writermohitagw15856/pm-claude-skills	Skill	1.5k	yesterday	MIT	A	80	Claude Code, Codex