Borrowing it
Nothing to install: this file belongs to kaininx/PlainTab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaininx/PlainTab/main/.agents/skills/improve-codebase-architecture/SKILL.mdgit clone --depth 1 https://github.com/kaininx/PlainTabWrote 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.
[](https://agentmods.dev/skills/kaininx/plaintab/improve-codebase-architecture)<a href="https://agentmods.dev/skills/kaininx/plaintab/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/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.
<a href="https://agentmods.dev/skills/kaininx/plaintab/improve-codebase-architecture"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/improve-codebase-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00536 |
| Opus 5.5 | $0.00016 | $0.00214 |
| Sonnet 5.5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00054 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve PlainTab Architecture
Use this skill for architecture review, not routine feature work. Adapted for PlainTab from Matt Pocock's improve-codebase-architecture skill.
Scope Guard
PlainTab values minimal, stable changes. Do not propose a rewrite. Do not change code during the review unless the user asks for implementation.
Respect:
.claude/rules/00-core.md- The relevant module rule under
.claude/rules/ - Startup invariants in
index.html - Storage ownership in
js/wallpaper/data.js - The no-build-tools/no-frameworks constraint
Vocabulary
- Module: a file or cohesive runtime area with an interface and implementation.
- Interface: everything callers must know to use the module, including ordering, config shape, errors, and side effects.
- Implementation: the code hidden behind that interface.
- Depth: how much behavior is hidden behind a small interface.
- Seam: a place behavior can change without editing every caller.
- Locality: how concentrated the knowledge, bug surface, and change surface are.
Review Process
- Pick one area, such as wallpaper sources, settings panel, storage migration, command palette, search, i18n, or startup.
- Read the module rule and the current files.
- Follow callers enough to understand who depends on the interface.
- Look for friction:
- Understanding one concept requires bouncing through many files.
- Callers must know too much ordering or storage detail.
- A module is mostly pass-through and does not buy locality.
- Two similar flows duplicate subtle behavior.
- The real behavior is hard to verify through an existing interface.
- Apply the deletion test: if deleting the module only moves the same complexity to callers, it is shallow; if deleting it spreads hidden complexity across callers, it is earning its keep.
Output
Present 2 to 5 candidates. For each:
- Files involved.
- Current friction.
- Proposed direction.
- Benefit in terms of locality, depth, and testability.
- Risk to startup, storage compatibility, wallpaper visibility, or UI quietness.
- Recommendation strength:
Strong,Worth exploring, orSpeculative.
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.
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.
- 2mo ago First seen · 57 lines · 41 tokens per session scan A 10fbc5bfb747
improve-codebase-architecture is a skill published in the GitHub repository kaininx/PlainTab (96 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 536 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…