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/nicolasyusim/better-codebase/better-maintainabilitynpx skills add NicolasYusim/better-codebase --skill better-maintainabilitygit clone --depth 1 https://github.com/NicolasYusim/better-codebaseWrote 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/nicolasyusim/better-codebase/better-maintainability)<a href="https://agentmods.dev/skills/nicolasyusim/better-codebase/better-maintainability"><img src="https://agentmods.dev/badge/skills/nicolasyusim/better-codebase/better-maintainability.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.01052 |
| Opus 5 | $0.00042 | $0.00526 |
| Sonnet 5 | $0.00017 | $0.00210 |
| Haiku 4.5 | $0.00008 | $0.00105 |
Grade A, and why
better-maintainability 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 3d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make local code predictable to read and change
Reduce the amount of state, context, and control flow a maintainer must hold in mind. Preserve cohesive narratives and established domain language.
Own the local implementation
Own findings inside functions, classes, modules, and cohesive components: naming, control flow, state, side effects, abstraction level, responsibility, and local change cost.
Escalate cross-module dependency problems to better-architecture, repeated knowledge to better-duplication, and unnecessary layers or speculative generality to better-simplicity.
Review workflow
1. Follow behavior, not metrics
Trace representative inputs through state changes, branches, effects, errors, and outputs. Identify what a maintainer must know to make a safe change.
Use complexity scores, function length, nesting depth, parameter count, and lint warnings only to locate code worth reading. Never report a threshold violation without demonstrating impact.
2. Inspect comprehension risks
Investigate:
- functions or classes with unrelated reasons to change;
- deeply nested conditionals that hide the primary path;
- control flow distributed across callbacks, flags, exceptions, or mutable state;
- hidden I/O, global mutation, time, randomness, or logging in apparently pure operations;
- names that conceal domain meaning, units, state, or side effects;
- mixed abstraction levels, such as policy decisions interleaved with serialization details;
- magic values whose meaning or ownership is unclear;
- booleans or enums that permit invalid combinations;
- broad exception handling that loses context or continues in an invalid state;
- order-dependent methods or partially initialized objects;
- comments that compensate for misleading structure or have drifted from behavior;
- dead paths, stale compatibility branches, or unused parameters;
- APIs whose return or mutation behavior surprises callers.
A long linear function can be clearer than ten tiny helpers. A short function can still hide dangerous state. Judge the reading and change path.
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.
- 3d ago First seen · 109 lines · 83 tokens per session scan A c2dfdc9e560b
better-maintainability is a skill published in the GitHub repository NicolasYusim/better-codebase (1 stars, last pushed 25d ago), licensed MIT. It adds 83 tokens to every session and 1,052 once invoked, about $0.0004 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-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
self-assessment
Interactive skill assessment with personalized learning path generation.
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…