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/optave/ops-codegraph-tool/deps-auditnpx skills add optave/ops-codegraph-tool --skill deps-auditgit clone --depth 1 https://github.com/optave/ops-codegraph-toolWhat 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.00027 | $0.02490 |
| Opus 5 | $0.00014 | $0.01245 |
| Sonnet 5 | $0.00005 | $0.00498 |
| Haiku 4.5 | $0.00003 | $0.00249 |
Grade A, and why
deps-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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deps-audit — Dependency Health Audit
Audit the project's dependency tree for security vulnerabilities, outdated packages, unused dependencies, and license compliance. Produce a structured report and optionally auto-fix safe updates.
Arguments
$ARGUMENTSmay contain--fixto auto-apply safe updates (patch/minor only)
Phase 0 — Pre-flight
- Confirm we're in the codegraph repo root (check for
package.jsonandpackage-lock.json) - Run
node --version— must be >= 20 - Run
npm --versionto capture toolchain info - Parse
$ARGUMENTS— setAUTO_FIX=trueif--fixis present - If
AUTO_FIXis set: Save the original manifests now, before any npm commands run, so pre-existing unstaged changes are preserved:git stash push -m "deps-audit-backup" -- package.json package-lock.json STASH_REF=$(git stash list --format='%gd %s' | grep 'deps-audit-backup' | head -1 | awk '{print $1}')STASH_REFis non-empty if and only if a stash entry was actually created. Do not use$?— modern git (2.16+) returns 0 even when nothing was stashed. Use[ -n "$STASH_REF" ](stash created) /[ -z "$STASH_REF" ](nothing stashed) for all branching. Use$STASH_REF(notstash@{0}) in all later stash drop/pop commands to avoid targeting the wrong entry.
Phase 1 — Security Vulnerabilities
Run npm audit --json and parse the output:
- Count vulnerabilities by severity:
critical,high,moderate,low,info - For each
criticalorhighvulnerability:- Record: package name, severity, CVE/GHSA ID, vulnerable version range, patched version, dependency path (direct vs transitive)
- Check if a fix is available (
npm audit fix --dry-run --json)
- Summarize: total vulns, fixable count, breaking-fix count
If AUTO_FIX is set: Run npm audit fix (non-breaking fixes only). Record what changed. Do NOT run npm audit fix --force — breaking changes require manual review.
Phase 2 — Outdated Dependencies
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 · 195 lines · 27 tokens per session scan A 02f3642e9df6
deps-audit is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 2,490 once invoked, about $0.0001 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
codespaces
Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal…
security-triage
Turn a large codebase into a short, ranked reading list of security-relevant code paths worth a human researcher's time, using the flyto-indexer MCP tools. Use when asked to find, prioritize, or triage potential vulnerabilities / taint flows / attack surface in a repository indexed (or indexable) by flyto-indexer …
devlens
Understand a codebase with the DevLens MCP — TypeScript, JavaScript, Python, Go, Rust, or Java (incl. React/Next.js/Node, FastAPI/Flask/Django, Spring Boot, Gin/Echo/chi/net-http, axum/actix/rocket). Query a precomputed graph of nodes (components, hooks, functions, classes, methods, structs, traits, routes) and typed…
archon
Multi-language dependency impact analysis for Java, JS/TS, and Python codebases. Answers "if I change this, what breaks?" Run /archon diff before refactoring, /archon analyze for full dependency maps.
codebase-intelligence
Query the codebase-intelligence CLI to understand TypeScript architecture, dependencies, blast radius, and risk before reading files. Use for any "how is this structured", "what breaks if I change X", "where is the complexity" question.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.