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.
npx agentmods add skills/kaininx/plaintab/improve-codebase-architecturenpx skills add kaininx/PlainTab --skill improve-codebase-architecturegit clone --depth 1 https://github.com/kaininx/PlainTabWhat 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.00041 | $0.00536 |
| Opus 5 | $0.00020 | $0.00268 |
| Sonnet 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 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.
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.
- 2d 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 (88 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 536 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…