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-simplicitynpx skills add NicolasYusim/better-codebase --skill better-simplicitygit 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-simplicity)<a href="https://agentmods.dev/skills/nicolasyusim/better-codebase/better-simplicity"><img src="https://agentmods.dev/badge/skills/nicolasyusim/better-codebase/better-simplicity.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.00080 | $0.01086 |
| Opus 5 | $0.00040 | $0.00543 |
| Sonnet 5 | $0.00016 | $0.00217 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
better-simplicity 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make the solution no more complex than the problem
Reduce the number of concepts a maintainer must understand while preserving real boundaries and intended behavior. Prefer boring, direct code when it expresses the domain accurately.
Own unnecessary complexity
Own complexity that exists without a demonstrated requirement, including unnecessary layers, indirection, generality, configuration, extensibility, and pattern machinery.
Do not own a valid boundary merely because it has multiple files. Ask better-architecture whether the boundary protects dependency direction, better-duplication whether an abstraction represents shared knowledge, and better-maintainability whether local code is hard to follow.
When orchestrated by better-codebase, act last and challenge every proposed change as well as the existing implementation.
Review workflow
1. Establish the real requirements
Identify current implementations, callers, variation points, runtime modes, extension contracts, and documented near-term constraints. Distinguish committed requirements from hypothetical future flexibility.
Do not treat might need, could support, or a generic type parameter as evidence of a requirement.
2. Count concepts and indirection
Trace a representative change or runtime path. Look for:
- interfaces with one implementation and no boundary rationale;
- factories that only call one constructor;
- wrappers that preserve the same API without adding policy or isolation;
- generic frameworks used by one concrete case;
- configuration values that never vary in supported deployments;
- strategy, visitor, builder, mediator, or event machinery without demonstrated variation;
- helper layers that make control flow harder to follow;
- data converted through multiple equivalent representations;
- extension points that make invalid states or combinations possible;
- custom utilities already provided clearly by the language or framework;
- defensive flexibility that has no owner, test, or removal condition.
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 · 111 lines · 80 tokens per session scan A bafe3074bcbf
better-simplicity is a skill published in the GitHub repository NicolasYusim/better-codebase (1 stars, last pushed 25d ago), licensed MIT. It adds 80 tokens to every session and 1,086 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.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
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.