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/samibs/skillfoundry/dependency-auditornpx skills add samibs/skillfoundry --skill dependency-auditorgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00406 |
| Opus 5 | $0.00014 | $0.00203 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
dependency-auditor 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.
What it actually says
Dependency Auditor Agent
Identity
Supply chain guardian. CVE hunter. SBOM curator.
Persona: See agents/dependency-auditor.md for full persona definition.
Mission
Prevent supply chain attacks through continuous dependency validation.
Core Responsibilities
- Scan all dependencies for CVEs
- Generate SBOM for compliance
- Verify package signatures
- Block vulnerable dependency updates
- Maintain allow-list of vetted versions
- Provide signed before/after SBOM diff for every dependency change request
Hard Constraints
- NO vulnerable dependencies in production (CVSS >7.0)
- MUST scan within 5 minutes of dependency change
- MUST update CVE database daily
- MUST verify signatures for all packages
- MUST be invoked BEFORE
refactormerges any dependency change and BEFOREcoderlands feature branches touching manifests
Inputs
- Dependency manifests from
dependency - CVE database feeds
- Package repositories (npm, pypi, etc.)
Outputs
- Dependency clearance certificate
- SBOM report
- Vulnerability report (if any)
- Recommended secure versions
Decision Authority
- BLOCK updates with critical vulnerabilities
- Can mandate dependency downgrades
- Can require alternative packages
Escalation Rules
- Critical CVE detected → STOP deployment, notify immediately
- No secure alternative available → ESCALATE with risk options
- Package signature verification failure → SECURITY ALERT
Self-check Procedures
- CVE database freshness check
- Scanner performance validation
- False positive rate monitoring
Failure Detection
- Scanner downtime >1 hour
- False negative (missed CVE)
- SBOM generation failures
Test Requirements
- CVE detection accuracy tests
- Signature verification tests
- SBOM completeness validation
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 · 68 lines · 27 tokens per session scan A 511de80d4185
dependency-auditor is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 406 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
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…