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/avi1234/claude-team-plugins/setup-dependenciesnpx skills add avi1234/claude-team-plugins --skill setup-dependenciesgit clone --depth 1 https://github.com/avi1234/claude-team-pluginsWrote 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/avi1234/claude-team-plugins/setup-dependencies)<a href="https://agentmods.dev/skills/avi1234/claude-team-plugins/setup-dependencies"><img src="https://agentmods.dev/badge/skills/avi1234/claude-team-plugins/setup-dependencies.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.00007 | $0.00210 |
| Opus 5 | $0.00003 | $0.00105 |
| Sonnet 5 | $0.00001 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade B, and why
setup-dependencies scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
6. {YOUR_PLUGIN}: Run `grep "{plugin-name}@{marketplace}" ~/.claude/settings.json` - warn if not found What it actually says
Check all required dependencies for this team's development environment:
- Check Node.js: Run
which nodeandnode --version- minimum version: {YOUR_MIN_VERSION} - Check npm: Run
which npm - Check git: Run
which git - Check gh CLI: Run
which gh- if not found, suggestbrew install gh && gh auth login- If found, verify auth:
gh auth status
- If found, verify auth:
- {YOUR_TOOL}: Run
which {tool}- fail if not found - {YOUR_PLUGIN}: Run
grep "{plugin-name}@{marketplace}" ~/.claude/settings.json- warn if not found - {YOUR_MCP}: Use ToolSearch with query "{mcp-name}" - fail if no tools found
Report status for each check. If any required checks fail, provide install commands.
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.
- 5d ago First seen · 18 lines · 7 tokens per session scan B 3678df535569
setup-dependencies is a skill published in the GitHub repository avi1234/claude-team-plugins (5 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 210 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
qa
This skill should be used when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".
backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
frontend
Use when building React components, optimizing performance, analyzing bundle sizes, scaffolding projects, implementing accessibility, reviewing frontend code quality, performing visual overhauls, or designing UI/UX systems.