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/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/update-yourself)<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>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.00000 | $0.01815 |
| Opus 5 | $0.00000 | $0.00907 |
| Sonnet 5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00181 |
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.
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.mdfrontmatter forwranglerVersionfield - If not found, check legacy location:
specifications/_CONSTITUTION.md - If
wranglerVersionfield missing, assume v1.0.0 (pre-versioning era)
Read current version:
- Read
skills/.wrangler-releases/CURRENT_VERSIONfrom 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 numberreleaseDate: Release datebreakingChanges: true/falsemigrationRequired: 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
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.
- 6d ago First seen · 321 lines · 0 tokens per session scan A 25afff8791de
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.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.