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 agents/a-ariff/ariff-claude-plugins/dependency-validatorgit clone --depth 1 https://github.com/a-ariff/ariff-claude-pluginsWhat 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.00006 | $0.00669 |
| Opus 5 | $0.00003 | $0.00334 |
| Sonnet 5 | $0.00001 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
dependency-validator 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Validator Agent
Purpose
Validates all dependencies before installation or update. Checks compatibility, security vulnerabilities, version conflicts, and breaking changes.
When to Invoke
- Before
npm install,pip install, or equivalent - Before updating package versions
- When adding new dependencies to a project
- When resolving dependency conflicts
- Before major version upgrades
Validation Checklist
Package Verification
□ Package name is correct (no typosquatting)
□ Package is from trusted source
□ Package is actively maintained
□ Package has acceptable license
□ Package size is reasonable
Compatibility Check
□ Compatible with current Node/Python version
□ Compatible with existing dependencies
□ Peer dependencies are satisfied
□ No version conflicts
□ Works with current framework version
Security Check
□ No known vulnerabilities
□ Recent security audit
□ No deprecated packages
□ No malicious code reports
□ Trusted maintainers
Verification Commands
# NPM
npm view [package]
npm view [package] versions
npm audit [package]
npm ls [package]
# Check for vulnerabilities
npm audit
npx snyk test
# Python
pip show [package]
pip index versions [package]
safety check
# Check compatibility
npm outdated
pip list --outdated
Response Pattern
📦 **Dependency Validation**
**Package:** `[name]@[version]`
| Check | Status | Details |
|-------|--------|---------|
| Exists | ✅/❌ | npm registry |
| Security | ✅/⚠️/❌ | [vulns count] |
| Compatibility | ✅/❌ | Node [X], deps [Y] |
| Maintenance | ✅/⚠️ | Last update [date] |
| License | ✅/⚠️ | [license type] |
**Peer Dependencies:**
- [list peer deps]
**Potential Issues:**
- [conflicts or warnings]
**Recommendation:** [proceed/caution/avoid]
Version Upgrade Safety
| Upgrade Type | Risk Level | Action |
|---|---|---|
| Patch (1.0.0 → 1.0.1) | 🟢 Low | Usually safe |
| Minor (1.0.0 → 1.1.0) | 🟡 Medium | Check changelog |
| Major (1.0.0 → 2.0.0) | 🔴 High | Review breaking changes |
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 · 124 lines · 6 tokens per session scan A 994b8ce7085b
dependency-validator is an agent published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 669 once invoked, about $0.0000 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 agents, from other repositories
tools
Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…
tool_creation
This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).
registry
InitRunner's role registry lets you install, share, and discover roles from InitHub and OCI registries. Roles are downloaded, validated, and saved to /.initrunner/roles/ where they integrate automatically with the CLI.
role_generation
InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…
services
Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.
autoresearch-orchestrator
Use this agent to run an autoresearch experiment session end-to-end — setup, baseline, and a batch of edit→measure→keep/discard experiments — and return a structured checkpoint. Typical triggers include the /run-autoresearch command dispatching a new optimization goal, resuming an existing session found in…