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-dependenciesnpx skills add NicolasYusim/better-codebase --skill better-dependenciesgit 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-dependencies)<a href="https://agentmods.dev/skills/nicolasyusim/better-codebase/better-dependencies"><img src="https://agentmods.dev/badge/skills/nicolasyusim/better-codebase/better-dependencies.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.00077 | $0.01167 |
| Opus 5 | $0.00039 | $0.00583 |
| Sonnet 5 | $0.00015 | $0.00233 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
better-dependencies 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve dependency health without chasing versions
Minimize supply-chain and maintenance burden while preserving compatibility. Treat an upgrade as a migration decision, not housekeeping.
Own dependency decisions
Own direct and transitive package necessity, version and runtime compatibility, health, deprecation, advisories, lockfiles, redundant capability, and migration planning.
Do not recommend architectural replacement merely because another library is fashionable. Coordinate boundary changes with better-architecture, custom-code simplification with better-simplicity, and upgrade verification with better-testing.
Review workflow
1. Inventory the dependency surface
Inspect every relevant manifest and lockfile in scope. Identify:
- direct, development, optional, peer, build, and platform dependencies;
- supported language, runtime, framework, and operating-system versions;
- workspaces, overrides, resolutions, patches, vendored code, and generated clients;
- imported APIs and the actual capability each direct package supplies;
- multiple lockfiles, unpinned sources, local paths, or manifest/lock mismatches;
- deployment and library consumers that constrain upgrades.
Use the ecosystem's native package manager for inspection. Do not rewrite a lockfile with a different tool.
2. Classify candidates
Investigate:
- published security advisories that affect the resolved version and usage;
- deprecated packages or APIs with an official migration path;
- unsupported versions relative to the project's runtime;
- abandoned packages only when maintenance evidence and risk are credible;
- packages that overlap substantially and increase bundle or maintenance cost;
- direct dependencies used for one trivial, stable operation available in the standard library;
- dependencies declared but not imported or required by tooling;
- version conflicts, duplicated majors, invalid peer ranges, or incompatible transitive constraints;
- lockfiles that are missing, stale, non-reproducible, or inconsistent with policy;
- framework or runtime upgrades blocked by a dependency.
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 · 127 lines · 77 tokens per session scan A f6c86593eb9c
better-dependencies is a skill published in the GitHub repository NicolasYusim/better-codebase (1 stars, last pushed 25d ago), licensed MIT. It adds 77 tokens to every session and 1,167 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.