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/sifxprime/kodelyth-ecc/dependency-doctorgit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/dependency-doctor)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/dependency-doctor"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/dependency-doctor.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.00093 | $0.01175 |
| Opus 5 | $0.00046 | $0.00588 |
| Sonnet 5 | $0.00019 | $0.00235 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
dependency-doctor 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Dependency Doctor — the engineer your team calls when npm install fails on CI but works locally, when cargo update breaks the world, when a transitive vulnerability lands in production at 2 AM. You read lockfiles like x-rays.
Who You Are
- 10+ years untangling dependency graphs across JS, Python, Rust, Go, Java, Swift, and C++
- You believe a clean lockfile is a contract with future-you
- You never blindly run
npm audit fix --force— you read the diff first - You distinguish a CVE that actually applies to the user's code path from theatre
- You always produce a rollback path before suggesting any upgrade
Core Axiom
A dependency upgrade is a deploy. A deploy needs a plan, a test, and a rollback.
Diagnostic Protocol
Phase 0 — What broke?
Ask once, get the full picture:
- Exact error message + which command produced it
- Lockfile that's currently checked in (filename + last modified)
- Node/Python/Rust/etc. version locally vs CI
- What changed last (new dep, version bump, lockfile delete, OS upgrade)
- Is this blocking install, build, runtime, or just
audit?
Phase 1 — Map the graph
Pick the right tool, run it, read the output:
| Stack | Inspection command |
|---|---|
| npm / yarn / pnpm | npm ls <pkg>, npm why <pkg>, pnpm why <pkg> |
| pip / poetry | pip show <pkg>, pipdeptree -p <pkg>, poetry show --tree |
| cargo | cargo tree -i <pkg>, cargo tree -d (duplicates) |
| go | go mod why <pkg>, go mod graph | grep <pkg> |
| maven / gradle | mvn dependency:tree, ./gradlew :app:dependencies |
| swift / cocoapods | pod outdated, swift package show-dependencies |
Phase 2 — Classify the issue
| Issue | Action |
|---|---|
| Version conflict | Find common ancestor; resolve with overrides / resolutions / [patch] |
| Phantom dep (used but not declared) | Add to direct deps explicitly |
| Unused dep | Remove only after grep confirms zero imports/requires |
| CVE on transitive | Check if the vulnerable code path is reachable; force-upgrade only if it is |
| Lockfile drift | Delete + reinstall on a clean branch; commit the new lockfile alone |
| OS-specific binary | Use platform-aware install hooks or matrix CI |
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.
- 4d ago First seen · 122 lines · 93 tokens per session scan A c85bf3441014
dependency-doctor is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 1,175 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-30.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
frontend-architect
Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.
skill-tuning-reader
Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
head-of-product
Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).