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 skills add the-open-agent/oss-skills --skill dependency-hygienegit clone --depth 1 https://github.com/the-open-agent/oss-skillsWrote 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/the-open-agent/oss-skills/dependency-hygiene)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/dependency-hygiene"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/dependency-hygiene/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/dependency-hygiene"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/dependency-hygiene.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00101 | $0.01922 |
| Opus 5 | $0.00051 | $0.00961 |
| Sonnet 5 | $0.00020 | $0.00384 |
| Haiku 4.5 | $0.00010 | $0.00192 |
Grade A, and why
dependency-hygiene 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 10d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Hygiene
Every dependency is code you did not write, cannot review continuously, and are nonetheless responsible for. For a library, each one is also imposed on every user downstream — a cost you spend on their behalf without asking.
Should you add it?
Run this before every npm install:
- How much of it will you use? One function from a 40-file package is usually a
copy (with attribution and license compliance — see
license-and-legal), not a dependency. - Could the standard library do it? Modern stdlibs cover far more than they did when most "small utility" packages were written.
- Is it maintained? Last release, open issue age, bus factor, response time on recent issues. A package with one maintainer and no release in three years is a future migration you have scheduled without noticing.
- What does it pull in? Check the transitive tree, not the direct entry.
- What is its license? Especially transitively.
- Does it run code at install time?
postinstall,setup.py,build.rs. - How hard is removal? If it is woven through your public API types, you have adopted its release cadence permanently.
npm view <pkg> dependencies maintainers time.modified
npx howfat <pkg> # true install size incl. transitives
npm ls --all <pkg> # who pulls this in
cargo tree -i <crate> # reverse dependency tree
pipdeptree -r -p <pkg>
Library authors: the bar is much higher than for applications. A dependency in a library is a dependency in every consumer's tree, a potential version conflict, and a row in their security scanner's report. Many successful libraries advertise zero runtime dependencies, and that is a feature users select on.
Ranges vs pinning
The rule that resolves most confusion:
| Applications | Libraries | |
|---|---|---|
| Manifest | Ranges are fine | Wide ranges, e.g. ^1.2.0 |
| Lockfile | Commit it | Commit it (for CI reproducibility) |
| Install in CI | npm ci / --locked |
npm ci, plus a job testing latest deps |
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.
- 10d ago First seen · 181 lines · 101 tokens per session scan A 604a107c2057
dependency-hygiene is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,922 once invoked, about $0.0005 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
opentrons-dev-update
Guide users through setting up or updating a local development environment for the Opentrons opentrons/opentrons monorepo. Use this skill whenever a user mentions setting up or updating Opentrons development, cloning the Opentrons repo, installing or refreshing dev dependencies for Opentrons, getting started…
opentrons-dev-setup
Guide users through setting up a local development environment for the Opentrons opentrons/opentrons monorepo. Use this skill whenever a user mentions setting up Opentrons development, cloning the Opentrons repo, installing dev dependencies for Opentrons, getting started contributing to Opentrons, or hits errors…
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
brandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…