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/oolab-labs/patchwork-os/dependency-auditnpx skills add Oolab-labs/patchwork-os --skill dependency-auditgit clone --depth 1 https://github.com/Oolab-labs/patchwork-osWhat 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.00000 | $0.00650 |
| Opus 5 | $0.00000 | $0.00325 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 2d 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.
This is a copy
100% identical to dependency-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installation
Copy this template to your Claude Desktop scheduled-tasks directory:
mkdir -p ~/.claude/scheduled-tasks/dependency-audit
cp /path/to/claude-ide-bridge/templates/scheduled-tasks/dependency-audit/SKILL.md \
~/.claude/scheduled-tasks/dependency-audit/SKILL.md
Then restart Claude Desktop to detect the new scheduled task. Configure the schedule in Claude Desktop settings under "Scheduled Tasks".
The bridge must be running when this task fires. Start it with
claude-ide-bridge --watchornpm run start-all.
Emergency stop: Set
CLAUDE_CODE_DISABLE_CRON=1in your environment to immediately halt all scheduled cron jobs mid-session. Useful if a task runs amok or you need to suppress scheduled runs temporarily.
name: dependency-audit description: Scan dependencies for security vulnerabilities and outdated packages. Run weekly via Claude Desktop scheduled tasks.
Dependency Security Audit
Scan all project dependencies for known security vulnerabilities.
Steps
- Call
getProjectInfoto detect the project type and package manager - Call
getSecurityAdvisoriesto check for known CVEs in dependencies - Call
auditDependenciesto run the package manager's native audit (npm audit, cargo audit, pip-audit, etc.) - Call
getDependencyTreeto understand the full dependency graph for any flagged packages
Report Format
# Dependency Audit — <date>
## Package Manager: <npm|cargo|pip|go>
## Vulnerabilities Found: <N total>
### Critical (N)
<package@version — CVE-XXXX-XXXXX — description>
Fix: upgrade to <version> | No fix available
### High (N)
<package@version — CVE-XXXX-XXXXX — description>
Fix: upgrade to <version> | No fix available
### Moderate (N)
<package@version — description>
## Outdated Packages
<package — current → latest> (only packages ≥1 major version OR ≥3 minor versions behind)
Direct: listed in package.json. Transitive: pulled in by direct dependencies.
## Recommended Actions
1. <specific upgrade command or action>
2. <specific upgrade command or action>
## Overall: SECURE | REVIEW NEEDED | ACTION REQUIRED
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.
- 2d ago First seen · 78 lines · 0 tokens per session scan A faccfb7e2891
dependency-audit is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 650 tokens. A static security scan graded it A with 0 findings. It is 100% identical to dependency-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.