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/dvnghiem/flowdeck/dependency-auditnpx skills add DVNghiem/FlowDeck --skill dependency-auditgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWrote 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/dvnghiem/flowdeck/dependency-audit)<a href="https://agentmods.dev/skills/dvnghiem/flowdeck/dependency-audit"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/dependency-audit.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.00034 | $0.00928 |
| Opus 5 | $0.00017 | $0.00464 |
| Sonnet 5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
dependency-audit 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.
Dependency Audit Skill
Checks dependencies for security vulnerabilities, outdated versions, and license issues before they cause problems in production.
When to Activate
Activate when:
- Preparing a production release
- Receiving a CVE alert for a dependency
- Adding a major new dependency
- It has been more than 30 days since last audit
Core Principles
- Security over convenience — patch vulnerabilities before releasing
- Patch before releasing — critical and high findings block deployment
- License compliance matters — GPL in a commercial product can create legal problems
Workflow
- Run security audit commands
- Triage findings by severity
- Check for outdated packages
- Check licenses of key dependencies
- Produce report with recommended actions
Audit Commands
# npm
npm audit # all vulnerabilities
npm audit --audit-level=moderate # moderate and above
npm audit fix # auto-fix safe upgrades
npm audit fix --force # force fix (may break things — test first)
# Check outdated packages
npm outdated
# Snyk (more comprehensive)
npx snyk test
npx snyk monitor
# Python
pip-audit # install: pip install pip-audit
pip list --outdated
# Rust
cargo audit # install: cargo install cargo-audit
# Check licenses
npx license-checker --summary
npx license-checker --onlyAllow 'MIT;Apache-2.0;BSD-2-Clause;BSD-3-Clause;ISC'
Severity Triage
| Severity | Action | Timeline |
|---|---|---|
| Critical | Fix immediately — do not deploy | Before next commit |
| High | Fix before release | Before next deployment |
| Moderate | Fix in next sprint | Within 2 weeks |
| Low | Track and fix eventually | Next maintenance window |
Common Vulnerability Patterns
- Prototype pollution — lodash <4.17.21, merge-deep <3.0.3
- Path traversal — file utility packages that accept user-controlled paths
- ReDoS — regex-based parsers (moment.js, validator.js older versions)
- Command injection — packages that shell out with user-controlled input
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 · 34 tokens per session scan A 2bfc29a18f63
dependency-audit is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 928 once invoked, about $0.0002 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-30.
Other skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.