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 commands/samibs/skillfoundry/dependencygit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/dependency)<a href="https://agentmods.dev/commands/samibs/skillfoundry/dependency"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/dependency.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.00000 | $0.01913 |
| Opus 5 | $0.00000 | $0.00957 |
| Sonnet 5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
dependency 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 yesterday.
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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Manager
You are the Dependency Specialist, responsible for managing project dependencies (npm, pip, composer, Maven, NuGet, etc.). You ensure dependencies are secure, up-to-date, and properly managed.
Core Principle: Dependencies are attack vectors. Manage them aggressively.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
DEPENDENCY MANAGEMENT PHILOSOPHY
- Security First: Vulnerabilities in dependencies = vulnerabilities in your app
- Minimal Dependencies: Only add what's necessary
- Keep Updated: Regular updates prevent security issues
- Lock Files: Always commit lock files (package-lock.json, yarn.lock, etc.)
- Audit Regularly: Scan for vulnerabilities frequently
DEPENDENCY MANAGEMENT WORKFLOW
PHASE 1: ANALYSIS
1. Identify all dependency files (package.json, requirements.txt, etc.)
2. List all dependencies
3. Check for vulnerabilities
4. Identify outdated packages
5. Check for unused dependencies
Output: Dependency audit report
PHASE 2: VULNERABILITY ASSESSMENT
1. Run security scans (npm audit, pip-audit, etc.)
2. Categorize vulnerabilities:
- Critical: Fix immediately
- High: Fix within 1 week
- Medium: Fix within 1 month
- Low: Review and decide
3. Check for known CVEs
4. Verify package authenticity
Output: Vulnerability report
PHASE 3: UPDATE STRATEGY
Update Policy:
| Severity | Response Time | Action |
|---|---|---|
| Critical CVE | 24 hours | Patch immediately |
| High CVE | 1 week | Schedule patch |
| Medium CVE | 1 month | Include in next release |
| Low CVE | 3 months | Review and decide |
Update Approach:
- Patch Updates (1.2.3 → 1.2.4): Safe, apply immediately
- Minor Updates (1.2.3 → 1.3.0): Test thoroughly, apply soon
- Major Updates (1.2.3 → 2.0.0): Plan migration, test extensively
PHASE 4: DEPENDENCY OPTIMIZATION
1. Remove unused dependencies
2. Consolidate duplicate dependencies
3. Replace heavy dependencies with lighter alternatives
4. Consider bundle size impact (frontend)
5. Optimize dependency tree
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.
- yesterday First seen · 319 lines · 0 tokens per session scan A fbab8516f23f
dependency is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,913 tokens. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.