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 commands/wbern/agent-instructions/upgrade-depsgit clone --depth 1 https://github.com/wbern/agent-instructionsWrote 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/commands/wbern/agent-instructions/upgrade-deps)<a href="https://agentmods.dev/commands/wbern/agent-instructions/upgrade-deps"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/upgrade-deps.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.00009 | $0.01357 |
| Opus 5 | $0.00005 | $0.00678 |
| Sonnet 5 | $0.00002 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade A, and why
upgrade-deps 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Upgrade Dependencies
Analyze available dependency upgrades, assess codebase safety signals, and guide the user through upgrade decisions.
Phase 1: Detect Environment
Scan for package manager and project setup:
| Check | How |
|---|---|
| Package manager | Look for pnpm-lock.yaml, yarn.lock, package-lock.json, bun.lockb |
| Lockfile present | Exists and tracked in git |
| Test script | package.json has test script |
| Test files | *.test.*, *.spec.*, __tests__/ exist |
| CI config | .github/workflows/, .gitlab-ci.yml, etc. |
| Type checking | tsconfig.json or jsconfig.json present |
Output:
## Environment
Package manager: pnpm
Lockfile: ✓ pnpm-lock.yaml (tracked)
Test script: ✓ "vitest run"
Test files: ✓ 16 test files found
CI config: ✓ .github/workflows/release.yml
Types: ✓ tsconfig.json
Phase 2: List Available Upgrades
Run the appropriate outdated command:
| Manager | Command |
|---|---|
| pnpm | pnpm outdated --format json |
| npm | npm outdated --json |
| yarn | yarn outdated --json |
| bun | bun outdated |
Group results by semver level:
## Available Upgrades
### Patch (low risk)
| Package | Current | Latest | Age |
|---------|---------|--------|-----|
| lodash | 4.17.20 | 4.17.21 | 6 months |
### Minor (medium risk)
| Package | Current | Latest | Age |
|---------|---------|--------|-----|
| vitest | 1.5.0 | 1.6.0 | 3 weeks |
### Major (review changelog)
| Package | Current | Latest | Age |
|---------|---------|--------|-----|
| typescript | 4.9.5 | 5.4.2 | 8 months |
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 · 206 lines · 9 tokens per session scan A ddb217ad8d7e
upgrade-deps is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,357 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.