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 skills add brunob54/superpowers-orchestrator --skill dependency-managementgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/dependency-management)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/dependency-management"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/dependency-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/dependency-management"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/dependency-management.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00156 | $0.01722 |
| Opus 5 | $0.00078 | $0.00861 |
| Sonnet 5 | $0.00031 | $0.00344 |
| Haiku 4.5 | $0.00016 | $0.00172 |
Grade A, and why
dependency-management 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Management
Update one thing at a time. Verify after each. Never batch major upgrades.
Why This Exists
Dependency updates look simple — bump a version number, run install, done. In practice, they're one of the most common sources of hard-to-diagnose breakage: silent API changes, peer dependency conflicts, transitive dependency resolution shifts, and build tool incompatibilities. This skill enforces a structured approach that catches breakage at the smallest possible blast radius.
Phase 1: Audit
Before changing any versions, understand what needs updating and why.
-
List outdated dependencies:
- Node.js:
npm outdatedoryarn outdated - Python:
pip list --outdatedorpip-audit - Go:
go list -m -u all - Rust:
cargo outdated - General: check the package manager's audit/outdated command
- Node.js:
-
Categorize each update by urgency:
- Security — CVE or advisory with known exploit. Update immediately.
- Breaking — major version bump with documented breaking changes. Plan carefully.
- Feature — minor/patch version with new features or non-breaking fixes. Low risk.
- Transitive — a dependency of a dependency. Usually handled by lockfile update.
-
Prioritize: Security > Breaking (if blocking other work) > Feature. Don't update everything at once — pick the highest-priority items first.
Phase 2: Impact Assessment
For each dependency to update (especially major versions):
-
Read the changelog/migration guide. Look for:
- Breaking API changes (renamed functions, removed options, changed signatures)
- Dropped platform/runtime support (minimum Node version, Python version, etc.)
- Peer dependency changes (requires React 18, drops support for React 16)
- Changed default behavior (opt-in → opt-out, strict mode, new warnings)
-
Search the codebase for usage of changed APIs. For each renamed/removed API, run separate searches for:
- Direct calls and type references
- String literals and dynamic access (
obj["methodName"]) - Import statements and re-exports
- Test files and mocks
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.
- 9d ago First seen · 134 lines · 156 tokens per session scan A 59935a05103e
dependency-management is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed 3d ago), licensed MIT. It adds 156 tokens to every session and 1,722 once invoked, about $0.0008 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
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
qa
Code review + QA vs Acceptance Criteria, including A+ status suggestions and review comment draft.