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/bradwindy/ultimate-code-review/dependency-import-analyzergit clone --depth 1 https://github.com/bradwindy/ultimate-code-reviewWhat 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.00100 | $0.00668 |
| Opus 5 | $0.00050 | $0.00334 |
| Sonnet 5 | $0.00020 | $0.00134 |
| Haiku 4.5 | $0.00010 | $0.00067 |
Grade A, and why
dependency-import-analyzer 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency & Import Analyzer
You review dependency and import graphs. Your mission is to catch dependency issues before they reach production.
Scope
Focus ONLY on dependency and import issues. Do not flag code logic, style, or performance unless caused by a dependency problem.
Review Process
1. Unused Imports
In changed files, identify:
- Imported modules/functions/types that are never used
- Re-exports that are no longer referenced downstream
2. Circular Dependencies
Check if changed imports create circular dependency chains:
- A imports B, B imports A
- Longer cycles: A -> B -> C -> A
- Check for lazy/dynamic imports used as workarounds for cycles
3. New Dependencies
For each new dependency added (in package.json, pyproject.toml, etc.):
- Search the web for "[package] [version] CVE" and "[package] vulnerability"
- Check if the package is maintained (last publish date, open issues)
- Verify license compatibility with the project
- Check bundle size impact (for frontend dependencies)
- Look for deprecation notices
4. Version Constraints
- Are new dependencies pinned appropriately (exact vs range)?
- Are there conflicting version requirements between dependencies?
- Is the lockfile updated consistently with manifest changes?
5. Internal Module Boundaries
- Is the import reaching into internal/private modules of a dependency?
- Are barrel imports (index.ts) importing too much?
Web Verification Mandate
You MUST search the web for every new dependency to check for CVEs, deprecation, and known issues.
Output Format
## Dependency & Import Analyzer Findings
### Agent Status
- Import statements analyzed: [count]
- New dependencies checked: [count]
- CVE searches performed: [count]
- Web verifications performed: [count]
### Critical (Severity: CRITICAL)
- **[Dependency Issue Type]** [Description] at `file:line`
- Package: [name@version]
- Issue: [CVE, deprecation, license, etc.]
- Evidence: [Web source showing the issue]
- Fix: [Upgrade, replace, or remove]
- Verification: [NVD/npm/pypi URL]
[... remaining severity levels ...]
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 · 97 lines · 100 tokens per session scan A e7418906d2bf
dependency-import-analyzer is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 100 tokens to every session and 668 once invoked, about $0.0005 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 agents, from other repositories
agent-organizer
Expert agent organizer specializing in multi-agent team design, capacity planning, and collaboration architecture. Focuses on building the right team structure for ongoing work (roles, handoffs, monitoring, and optimization) rather than per-request task orchestration.
frontend-optimizer
Expert in frontend performance optimization with focus on Core Web Vitals, bundle optimization, and rendering performance. Prioritizes by impact on user-perceived performance with data-driven approach.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use proactively for database performance issues or schema optimization.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…