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 omergocmen/vibe-coder-kit --skill dependency-auditgit clone --depth 1 https://github.com/omergocmen/vibe-coder-kitWrote 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/omergocmen/vibe-coder-kit/dependency-audit)<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/dependency-audit"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/dependency-audit/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/omergocmen/vibe-coder-kit/dependency-audit"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/dependency-audit.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.00039 | $0.01330 |
| Opus 5.5 | $0.00016 | $0.00532 |
| Sonnet 5.5 | $0.00008 | $0.00266 |
| Haiku 4.5 | $0.00004 | $0.00133 |
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 1mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit Skill
When to Trigger
- Before any production release
- Monthly cadence (add to sprint planning)
- After a CVE is publicly announced that might affect your stack
- When a team member says "we should update our packages"
- Before onboarding a new contributor (known-safe baseline)
Step-by-Step Process
1. Detect Package Ecosystem
Identify which package managers are in use:
package.json → npm / yarn / pnpm (Node.js)
requirements.txt → pip (Python)
pyproject.toml → pip / poetry (Python)
Gemfile → bundler (Ruby)
go.mod → go modules (Go)
Cargo.toml → cargo (Rust)
Run the audit steps for each ecosystem found.
2. Security Vulnerability Scan
Node.js
npm audit
# or
yarn audit
# or
pnpm audit
Python
pip install pip-audit
pip-audit
General (all ecosystems)
# If using GitHub: check Security tab → Dependabot alerts
# If using Snyk:
snyk test
Triage each finding:
| Severity | Action |
|---|---|
| Critical | Fix immediately before any other work |
| High | Fix before next release |
| Medium | Schedule for current sprint |
| Low | Track, fix when touching related code |
3. Outdated Package Scan
Node.js
npm outdated
Python
pip list --outdated
For each outdated package, check:
- How many major versions behind? (1 minor = low urgency, 2+ major = high urgency)
- Is it a direct or transitive dependency?
- Does the changelog mention breaking changes?
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.
- 1mo ago First seen · 219 lines · 39 tokens per session scan A 66d5a0659672
dependency-audit is a skill published in the GitHub repository omergocmen/vibe-coder-kit (94 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,330 once invoked, about $0.0002 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
tdd
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/ /, verify APIs via web search, then implement in tiny test-verified steps.
electron-desktop-builder
Converts a web app (Express, React, Vite, Next.js) into an Electron desktop app. Use when starting a new Electron project from an existing web app, when setting up electron-builder for the first time, when creating main.ts/preload.ts boilerplate, when generating icon assets, or when configuring NSIS installers.…
ai-skill-auditor
A universal, dependency-free Node.js tool to statically audit AI Skills and local agents for malicious patterns.
c4-architecture-c4-architecture
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
data-engineering-data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.