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 skills add lfyxhappy/lfcode --skill dependency-upgradergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/skills/lfyxhappy/lfcode/dependency-upgrader)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/dependency-upgrader"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/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/skills/lfyxhappy/lfcode/dependency-upgrader"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/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.00051 | $0.00344 |
| Opus 5.5 | $0.00020 | $0.00138 |
| Sonnet 5.5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
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 1mo 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.
What it actually says
Dependency Upgrader
Change dependencies deliberately and leave the lockfile consistent with the repository.
Workflow
- Identify the workspace package, package manager, manifest, lockfile, supported runtime, and the exact requested version range.
- Check
git statusand diffs before editing. Search for direct imports, peer constraints, scripts, generated files, and package-specific compatibility tests. - Review locally available package metadata or release information. If authoritative information is unavailable, state that limitation instead of inventing compatibility claims.
- Update only the requested manifest and the lockfile entries required by the package manager. Preserve unrelated user edits and avoid opportunistic upgrades.
- Run the package's install or consistency check, focused tests, typecheck, and build when the dependency affects generated or shipped output.
- Inspect the final diff for transitive churn, license or security concerns, and accidental credentials before handoff.
Boundaries
- Use Bun workspace commands where this repository requires Bun. Do not silently switch package managers.
- Do not run arbitrary install scripts, execute untrusted package code, or change registry credentials without explicit authorization.
- Do not claim an upgrade is safe solely because installation succeeded; distinguish resolution, compilation, tests, and runtime verification.
Recovery
If resolution or tests fail, preserve the failure evidence, identify the incompatible constraint, and propose a bounded rollback or version adjustment. Never discard unrelated worktree 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.
- 1mo ago First seen · 28 lines · 51 tokens per session scan A 06afee947a14
dependency-upgrader is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 344 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Design doc (write -> review loop)
Draft a design document and iterate writer/reviewer subagents until consensus.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.
Review changes (multi-agent)
Delegate read-only reviewers over the local changes/branch and consolidate findings.