update-yourself

update-yourself is a command for Claude Code from bacchus-labs/wrangler. It costs 0 tokens per session (1,815 once invoked), scanned A, original, MIT.

A migration guide for updating a Wrangler project to the latest available version. Wrangler is the project framework or workflow this add-on is designed to update.

In plain words
What is it for?
Use it to read the project's current version, compare it with the plugin version, find the intervening releases, and produce step-by-step migration instructions.
Why use it?
It identifies the version gap and the required changes across the releases in between, so an upgrade is easier to carry out safely.

Command for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions Claude Code.

Part of the wrangler plugin — 25 skills, 16 commands, 13 agents shipped together

Good fit Use it to read the project's current version, compare it with the…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bacchus-labs/wrangler/update-yourself
Install

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.

Clone the repo
git clone --depth 1 https://github.com/bacchus-labs/wrangler

Made for: Claude Code.

Or install wrangler, the plugin that ships this one along with the rest of its 25 skills, 16 commands, 13 agents.

Wrote 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.

agentmods badge for update-yourself

README.md
[![agentmods](https://agentmods.dev/badge/commands/bacchus-labs/wrangler/update-yourself.svg)](https://agentmods.dev/commands/bacchus-labs/wrangler/update-yourself)
Your own site
<a href="https://agentmods.dev/commands/bacchus-labs/wrangler/update-yourself"><img src="https://agentmods.dev/badge/commands/bacchus-labs/wrangler/update-yourself.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,815 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01815
Opus 5 $0.00000 $0.00907
Sonnet 5 $0.00000 $0.00363
Haiku 4.5 $0.00000 $0.00181

Measured 6d ago against content hash 25afff8791de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

update-yourself 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 6d 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.

.wrangler/memory/knowledge-base/reference-prompts/commands/update-yourself.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the user update their wrangler project to the latest version.

Your Task

Generate clear, step-by-step migration instructions for upgrading a wrangler project from its current version to the latest version. The instructions should be optimized for AI execution (not bash scripts).

Steps to Execute

1. Detect Version Gap

Read project version:

  • Check .wrangler/governance/CONSTITUTION.md frontmatter for wranglerVersion field
  • If not found, check legacy location: specifications/_CONSTITUTION.md
  • If wranglerVersion field missing, assume v1.0.0 (pre-versioning era)

Read current version:

  • Read skills/.wrangler-releases/CURRENT_VERSION from wrangler plugin directory
  • This is the latest available wrangler version

Compare versions:

  • If versions match: "✅ Already up to date (v{version})"
  • If project > current: "⚠️ Project version ({project}) is ahead of plugin ({current}). Plugin may need updating."
  • If project < current: Continue with migration plan

2. Determine Migration Scope

List version gap:

  • Identify all versions between project version and current version
  • Example: If project=1.0.0, current=1.3.0 → Gap versions: [1.1.0, 1.2.0, 1.3.0]

Load release notes:

  • For each version in gap, read skills/.wrangler-releases/{version}.md
  • Extract from frontmatter:
    • version: Version number
    • releaseDate: Release date
    • breakingChanges: true/false
    • migrationRequired: true/false

Filter to breaking changes:

  • Only include versions where breakingChanges: true
  • If no breaking changes exist, this is a non-breaking update

3. Generate Migration Instructions

Create a comprehensive migration plan with:

  • Overview of what's changing
  • Step-by-step instructions for AI to execute
  • Verification steps after each major change
  • Rollback instructions if migration fails

Important: Instructions should be written for an AI assistant to execute, NOT bash scripts for humans to run.

Output Format

Read the full file on GitHub · 321 lines

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.

  1. 6d ago First seen · 321 lines · 0 tokens per session scan A 25afff8791de

Subscribe to this mod's changes

update-yourself is a command published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,815 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.