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-architecturenpx skills add NicolasYusim/better-codebase --skill better-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/nicolasyusim/better-codebase/better-architecture"><img src="https://agentmods.dev/badge/skills/nicolasyusim/better-codebase/better-architecture.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.00072 | $0.01193 |
| Opus 5 | $0.00036 | $0.00596 |
| Sonnet 5 | $0.00014 | $0.00239 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
better-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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve architecture without imposing a template
Make the system easier to change by putting responsibilities and dependencies in the right places. Judge architecture relative to the product, team, scale, runtime, and existing constraints.
Own the system-level boundary
Own findings about relationships between modules, packages, services, layers, and public contracts.
Do not own:
- local readability or control flow inside a module —
better-maintainability; - textual repetition or repeated business knowledge —
better-duplication; - unnecessary indirection in an otherwise valid boundary —
better-simplicity; - weak behavioral protection —
better-testing; - version or package health —
better-dependencies.
Report a cross-domain issue once under the skill that owns its root cause.
Review workflow
1. Map the actual system
Identify entry points, deployable units, packages, internal modules, public APIs, persistence, external services, event flows, background work, and ownership boundaries. Inspect imports, calls, configuration, schemas, and tests rather than inferring architecture from folder names.
State whether the codebase is a small application, modular monolith, library, service collection, plugin, or another shape. Do not evaluate every shape against enterprise architecture.
2. Trace important change paths
Follow representative behavior end to end. Ask:
- Which modules know about which other modules?
- Where is policy decided and where are effects performed?
- Does a small business change require edits across unrelated layers?
- Do high-level rules depend directly on volatile infrastructure details?
- Are public contracts explicit and stable?
- Can a subsystem be understood and tested through a narrow surface?
Use repository history when available to support claims about files that change together. Do not require history for a finding when current dependency evidence is sufficient.
3. Inspect architectural risks
Treat these as investigation leads:
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.
- 4d ago First seen · 130 lines · 72 tokens per session scan A 6a8cda29051a
better-architecture is a skill published in the GitHub repository NicolasYusim/better-codebase (1 stars, last pushed 26d ago), licensed MIT. It adds 72 tokens to every session and 1,193 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-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
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-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.