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 bacchus-labs/wrangler --skill dependency-opportunity-scannergit clone --depth 1 https://github.com/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/dependency-opportunity-scanner)<a href="https://agentmods.dev/skills/bacchus-labs/wrangler/dependency-opportunity-scanner"><img src="https://agentmods.dev/badge/skills/bacchus-labs/wrangler/dependency-opportunity-scanner/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/bacchus-labs/wrangler/dependency-opportunity-scanner"><img src="https://agentmods.dev/badge/skills/bacchus-labs/wrangler/dependency-opportunity-scanner.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.00045 | $0.03999 |
| Opus 5 | $0.00023 | $0.01999 |
| Sonnet 5 | $0.00009 | $0.00800 |
| Haiku 4.5 | $0.00005 | $0.00400 |
Grade A, and why
dependency-opportunity-scanner 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 10d 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 — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the dependency opportunity scanner workflow coordinator. Your job is to identify code that could be simplified by adopting existing libraries, implement the refactoring in an isolated worktree, and submit a PR for human review.
Core Responsibilities
Skill Usage Announcement
MANDATORY: When using this skill, announce it at the start with:
🔧 Using Skill: dependency-opportunity-scanner | [brief purpose based on context]
Example:
🔧 Using Skill: dependency-opportunity-scanner | [Provide context-specific example of what you're doing]
This creates an audit trail showing which skills were applied during the session.
- Scan codebase for reimplemented functionality that exists in libraries
- Analyze cost/benefit of adopting each library
- Create isolated git worktree for implementation
- Implement library integration with tests
- Submit PR with detailed rationale and impact analysis
Execution Strategy: Five-Phase Workflow
This is a workflow skill coordinating multiple phases with parallel analysis.
Phase 1: Codebase Analysis (Parallel)
Purpose: Identify patterns and custom implementations that might be library candidates.
Launch three parallel analysis agents:
Agent A: Pattern Detection
Task: Identify common patterns that libraries typically solve
Approach:
- Scan codebase for common patterns:
- Date/time manipulation and formatting
- HTTP client implementations
- Logging and error handling utilities
- Validation and schema checking
- CLI argument parsing
- Configuration management
- Testing utilities
- Data transformation (CSV, JSON, XML parsing)
- Cryptographic operations
- File system utilities
- String manipulation helpers
- Promise/async utilities
- For each pattern found:
- Count lines of custom code
- Assess complexity (simple wrapper vs. complex logic)
- Identify dependencies on custom implementation
- Output: List of patterns with LOC and complexity ratings
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.
- 10d ago First seen · 616 lines · 45 tokens per session scan A c92c4fbdd442
dependency-opportunity-scanner is a skill published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 3,999 once invoked, about $0.0002 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…