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 dean0x/devflow --skill dependenciesgit clone --depth 1 https://github.com/dean0x/devflowWrote 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/dean0x/devflow/dependencies)<a href="https://agentmods.dev/skills/dean0x/devflow/dependencies"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/dependencies/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/dean0x/devflow/dependencies"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/dependencies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 77 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00015 | $0.00927 |
| Opus 5.5 | $0.00006 | $0.00371 |
| Sonnet 5.5 | $0.00003 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependencies Patterns
Domain expertise for dependency management and security analysis. Use alongside devflow:review-methodology for complete dependency reviews.
Iron Law
EVERY DEPENDENCY IS AN ATTACK SURFACE
Each package you add is code you didn't write but must trust. Minimize dependencies. Pin versions. Audit regularly. A single compromised transitive dependency can compromise your entire application. "It's a popular package" is not a security review.
Dependency Categories
1. Security Vulnerabilities
Known CVEs, vulnerable version ranges, malicious packages.
Violation: Wide version range includes vulnerable versions
{ "lodash": "^4.0.0" } // Includes vulnerable 4.17.0-4.17.20
Correct: Pin to safe version
{ "lodash": "^4.17.21" } // First safe version
2. Version Management
Unpinned versions, missing lockfiles, dependency conflicts.
Violation: Unpinned allows any version
{ "express": "*", "lodash": "latest" }
Correct: Pin with lockfile
{ "express": "^4.18.2" } // + committed lockfile
3. Dependency Health
Outdated packages, unused dependencies, unnecessary heavy packages.
Violation: Heavy dependency for simple task
{ "moment": "^2.29.4" } // 300KB for date formatting
Correct: Use native or lighter alternative
new Date().toLocaleDateString(); // Native
4. License Issues
Incompatible licenses (GPL in MIT project), missing licenses.
Violation: GPL in proprietary code
# GPL-3.0: some-package # Requires your code to be GPL too!
Correct: Use permissive licenses only
npx license-checker --failOn "GPL-3.0;AGPL-3.0"
5. Supply Chain Risks
Deep transitive dependencies, unmaintained packages, typosquatting.
Violation: Typosquatted package
{ "loadsh": "1.0.0" } // Typosquat of "lodash"
Correct: Verify package authenticity
npm view loadsh # Check downloads, repo, maintainers
What ships with it
3 files 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.
- 7d ago Changed · -4 tokens per session 27d5e6b5b905
- 1mo ago First seen · 142 lines · 19 tokens per session scan A de8abf5432fa
dependencies is a skill published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.
code-review
You are a senior code reviewer. You receive diffs via stdin.
review
Adversarial fresh-context review and risk check of an increment before it ships; every finding cites path:line and is re-verified. Use for "review", "qa", "quality check", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.