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/eveld/claude/upgradegit clone --depth 1 https://github.com/eveld/claudeWhat 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.00000 | $0.02185 |
| Opus 5 | $0.00000 | $0.01092 |
| Sonnet 5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
upgrade 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 3d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Plugin Version
Upgrade the workflows plugin from one version to another, handling both automated migrations and edge cases that require reasoning.
Initial Response
When invoked, automatically detect versions and show upgrade path:
Workflows Plugin Upgrade
Detected current version: v1.2.0
Latest available version: v1.3.0 (from CHANGELOG.md)
Upgrade path: v1.2.0 → v1.3.0
Changes in v1.3.0:
- Feature-centric directory structure
- Changelog tracking system
- Milestone-based planning
- Agent orchestration
Proceed with upgrade? [Yes/Cancel]
No parameters needed: Command automatically upgrades to latest version from CHANGELOG.md
Workflow
Step 1: Detect Current and Target Versions
- Create version file if missing:
- If
migrations/version.txtdoesn't exist, create it - Detect from indicators:
thoughts/shared/exists = v1.2.0, else = v1.3.0 - If already on v1.3.0, exit with "Already on latest version"
- If
- Read current version: Parse
current:frommigrations/version.txt - Validate version against indicators:
- If file says v1.2.0 but
thoughts/NNNN-*/directories exist, ask user:Your installation state is unclear: - Version file says v1.2.0 - But feature directories exist (v1.3.0+ pattern) Did you manually migrate or create feature directories? Options: 1. Assume v1.3.0 (skip migration) 2. Re-detect from indicators 3. Cancel and let me investigate - If file says v1.3.0 but
thoughts/shared/exists, that's OK (backward compatible)
- If file says v1.2.0 but
- Read target version: Latest version from CHANGELOG.md (first
## [X.Y.Z]entry) - Show upgrade path: "Current: v1.2.0, Target: v1.3.0"
- Context: Read
migrated_from:line for upgrade report
Step 2: Calculate Version Delta
- Read version-specific upgrade definitions
- Determine what changed between versions:
- v1.2.0 → v1.3.0: Directory structure, changelog system, milestones, agents
- v1.3.0 → v1.4.0 (future): [whatever changes in that version]
- Identify specific migrations needed for this delta
- Show user what will change:
Upgrading from v1.2.0 to v1.3.0: Changes in v1.3.0: - New directory structure (thoughts/NNNN-description/) - Changelog tracking system - Milestone-based planning - Agent orchestration patterns Your installation needs: - Migrate 15 documents from thoughts/shared/ - No changelog or milestone updates (those are for new plans)
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.
- 3d ago First seen · 269 lines · 0 tokens per session scan A 288c88dcb6fd
upgrade is a command published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,185 tokens. 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-31.
Other commands, from other repositories
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.