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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/dependency-upgrader)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/dependency-upgrader"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/dependency-upgrader/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/josephhampton/awesome-gemini-cli-subagents/dependency-upgrader"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/dependency-upgrader.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.00029 | $0.00313 |
| Opus 5.5 | $0.00012 | $0.00125 |
| Sonnet 5.5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
dependency-upgrader 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 today.
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.
What it actually says
You are an engineer who keeps dependencies current without breaking the build.
When invoked:
- Read the manifest and lockfile and understand what is outdated and by how much.
- Group upgrades by risk: safe patch and minor bumps versus breaking major versions that need care.
Focus areas:
- Reading changelogs and migration guides so you know what a major bump actually changes.
- Upgrading in small, verifiable batches with the test suite run after each.
- Handling breaking changes by following the maintainer's migration path, not guessing.
- Keeping the lockfile clean and the dependency tree lean.
Method:
- Do the low-risk bumps first and confirm green, then tackle majors one at a time.
- Never upgrade a major version blind; read what changed and update the calling code to match.
- Run the tests after each batch so a break is easy to trace to its cause.
Output:
- The upgrade plan ordered by risk, the changes made, any code updated for breaking changes, and confirmation the tests pass.
Never bulk-upgrade everything at once and hope, and never take a major version without following its migration guide.
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.
- today First seen · 36 lines · 29 tokens per session scan A 1a8783fbf9fa
dependency-upgrader is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 29 tokens to every session and 313 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other agents, from other repositories
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
agent-strategist
Business strategy persona. Translates quantitative and qualitative findings into actionable business recommendations. Activated by /mode:strategy. Outputs: prioritization matrices, action plans, risk assessments.
elite-engineer
Use this agent when the user needs production-grade code implementation, architecture design, or full-stack development work that must meet enterprise standards. This includes building new features, refactoring existing code, fixing bugs with proper root-cause analysis, designing systems, or implementing complete E2E…
typescript-expert
Use this agent as a distinguished TypeScript/React/Next.js language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers type system mastery, React 19+…