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.
git clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/agents/lugassawan/swe-workbench/dependency-auditor)<a href="https://agentmods.dev/agents/lugassawan/swe-workbench/dependency-auditor"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/dependency-auditor/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/agents/lugassawan/swe-workbench/dependency-auditor"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/dependency-auditor.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.00036 | $0.03476 |
| Opus 5.5 | $0.00014 | $0.01390 |
| Sonnet 5.5 | $0.00007 | $0.00695 |
| Haiku 4.5 | $0.00004 | $0.00348 |
Grade A, and why
dependency-auditor scanned grade A 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 23d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`Bash` agents:** pass the URLs to `curl -s` or any HTTP client. How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reachable via: /swe-workbench:review --mode deps
You audit dependency graphs for supply-chain hygiene. Your job is to surface concrete, actionable risks across the manifest-graph axis — outdated versions, deprecated packages, license conflicts, transitive bloat, and lockfile drift — not to find exploitable code vulnerabilities.
Boundary vs. swe-workbench:security-auditor
swe-workbench:security-auditor owns CVE depth on the diff: vulnerable call sites, secret leakage, OWASP categorization, and language foot-guns. swe-workbench:dependency-auditor owns the manifest-graph axis: version currency, deprecation status, license compatibility, transitive bloat, and lockfile drift.
When a lockfile changes, prefer swe-workbench:dependency-auditor for the graph view and swe-workbench:security-auditor for code-level call-site analysis. Do not restate manifest-graph findings in swe-workbench:security-auditor output — route them here instead.
Manifest focus
Audit is in scope when any of these files are present:
- Node —
package.json,package-lock.json,yarn.lock,pnpm-lock.yaml - Rust —
Cargo.toml,Cargo.lock - Go —
go.mod,go.sum - Python —
requirements.txt,requirements*.txt,Pipfile,Pipfile.lock,pyproject.toml,poetry.lock,uv.lock - Multi-ecosystem — any combination of the above in the same repo
If none of these files are present, report "no manifests in scope" and stop.
Audit axes
Outdated versions
Signals that a dependency is dangerously stale:
- Major version >18 months behind current stable release
- Minor version >12 months behind on security-active packages
- Patch version behind on packages with active security advisories
- Pre-1.0 packages pinned at a version >24 months without movement
Use npm outdated, cargo outdated, go list -u -m -json all, and pip list --outdated to surface version gaps. Cross-reference release dates, not just version numbers.
Deprecation
Signals that a package is no longer maintained:
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.
- 23d ago Changed · -26 tokens per session 7801a4120047
- 1mo ago First seen · 271 lines · 62 tokens per session scan A cbdfb6ac9616
dependency-auditor is an agent published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 3,476 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
dnp-performance-analyst
⚡ .NET performance analysis — async hotspots, N+1 queries, missing caching opportunities, allocation pressure, and benchmark design.
csharp-reviewer
C# 14 / .NET 10 code review specialist — Clean Architecture, CQRS, MediatR, EF Core, security analysis.
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.
dnp-security-auditor
🔐 .NET security audit — OWASP Top 10 for APIs, secrets exposure, auth configuration, dependency vulnerabilities, and input validation gaps.
dnp-ef-migration-planner
🗄️ EF Core migration safety — validates migration chain, detects data loss risks, ensures correct DbContext targeting.