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/goondocks-co/open-agent-kit/dependency-auditnpx skills add goondocks-co/open-agent-kit --skill dependency-auditgit clone --depth 1 https://github.com/goondocks-co/open-agent-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/goondocks-co/open-agent-kit/dependency-audit)<a href="https://agentmods.dev/skills/goondocks-co/open-agent-kit/dependency-audit"><img src="https://agentmods.dev/badge/skills/goondocks-co/open-agent-kit/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.00068 | $0.00952 |
| Opus 5 | $0.00034 | $0.00476 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Audit dependencies across connected swarm nodes to find version conflicts, outdated packages, and standardization opportunities.
Workflow
1. Verify Connectivity
swarm_status()
swarm_nodes()
If disconnected or fewer than 2 nodes are available, inform the user — a cross-project audit needs multiple projects to compare.
2. Gather Dependency Data
Search for dependency-related information across the swarm:
# Package manifests and dependency choices
swarm_search(query="package.json dependencies pyproject.toml requirements", search_type="all", limit=20)
# Dependency decisions and rationale
swarm_search(query="dependency choices and version decisions", search_type="memory", limit=20)
# Known dependency issues
swarm_search(query="dependency conflicts outdated packages security vulnerabilities", search_type="memory", limit=15)
Also read the local project's dependency manifests for comparison:
# Check what exists locally
Glob("**/package.json")
Glob("**/pyproject.toml")
Glob("**/requirements*.txt")
Glob("**/Cargo.toml")
Glob("**/go.mod")
Read the relevant manifests to extract dependency lists.
3. Fetch Details for Key Findings
For search results that indicate conflicts or interesting patterns:
swarm_fetch(ids=["<chunk-id>"], project_slug="<project>")
4. Write the Audit Report
Write to oak/insights/dependency-audit-report.md:
# Dependency Audit Report
> Generated: YYYY-MM-DD | Projects audited: N
## Executive Summary
Brief overview of findings — number of conflicts found, critical risks, and
top recommendations for alignment.
## Version Conflict Analysis
| Package | Project A | Project B | Risk Level | Notes |
|---------|-----------|-----------|------------|-------|
| ... | v1.2.3 | v3.0.0 | High | Major version mismatch |
Focus on:
- Same package at different major versions across projects
- Pinned versions that differ significantly
- Transitive dependency risks
## Security Assessment
Flag dependencies that may pose risks:
- Very outdated packages (2+ major versions behind current)
- Packages with known deprecation notices
- Unusual or unmaintained dependencies
## Standardization Recommendations
| Action | Packages | Projects Affected | Priority |
|--------|----------|-------------------|----------|
| Align to v4.x | react | project-a, project-b | High |
| ... | ... | ... | ... |
Suggest:
- Packages that should converge to one version
- Shared internal packages that could reduce duplication
- Upgrade paths for outdated dependencies
## Shared Dependencies
Packages used across multiple projects (potential extraction candidates):
- List common utilities, frameworks, and tools
- Note where versions already align (positive signal)
What ships with it
2 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.
- 5d ago First seen · 144 lines · 68 tokens per session scan A abe1822aca02
dependency-audit is a skill published in the GitHub repository goondocks-co/open-agent-kit (10 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 952 once invoked, about $0.0003 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
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…
gsap-core
Official GSAP skill for the core API — gsap.to(), from(), fromTo(), easing, duration, stagger, defaults, gsap.matchMedia() (responsive, prefers-reduced-motion). Use when the user asks for a JavaScript animation library, animation in React/Vue/vanilla, GSAP tweens, easing, basic animation, responsive or reduced-motion…
grill-me
针对方案或设计的高强度追问式面试（adversarial design review / grill session），暴露假设漏洞与缺失约束，过程中同步维护领域模型（术语表和 ADR）。手动调用 /grill-me。.