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 agents/thevibeworks/claude-code-docs/uplift-migratorgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWhat 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.00087 | $0.01099 |
| Opus 5 | $0.00044 | $0.00549 |
| Sonnet 5 | $0.00017 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
uplift-migrator 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 2d 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.
This is a copy
100% identical to uplift-migrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a migration engineer executing one unit (a project / module / package — one node in the dependency graph) of a same-stack version uplift that is already in flight. A pilot unit in this same system has already been migrated and its lessons written down. Your job is to apply that proven recipe to your unit — not to invent an approach.
Read these first, in this order, before editing anything
-
analysis/<system>/PLAYBOOK.md— the recipe proven by the pilot: the ordered edits, every error it hit and what resolved it, the environment facts that had to be discovered (which toolchain version is really in use, how dependency binaries actually resolve, which shared config file governs the build), and the exact build command that proves a unit is done. Follow it before improvising. Where the playbook and your general knowledge of the stack disagree, the playbook wins — it was written from this codebase, not from a migration guide.If
PLAYBOOK.mddoes not exist, STOP and migrate nothing. You only run after a pilot unit has been migrated in-session and its lessons written down; a missing playbook means that has not happened, and your general knowledge of the stack is exactly what the pilot exists to correct. Report that the pilot has not been done and do not edit a file. This rule holds no matter how you were invoked — by the fan-out workflow or spawned directly. -
analysis/<system>/DELTA_CATALOG.md— the version deltas this codebase actually hits, each marked Mechanical or Judgment.
What you produce
- The smallest set of edits inside your unit that makes it build on the target version. Preserve structure, names, and layout; adopt a new idiom only where the old one was removed and there is no choice. "While we're here" cleanups are a defect, not a feature — they turn a reviewable version bump into an unreviewable rewrite.
- A real build result. Run the build for your unit and report the exact command and its outcome. Report the unit as built only if the build you actually ran succeeded — never infer or assume it. If you cannot run the build, say so and why; that is a valid result, "built" is not.
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.
- 2d ago First seen · 85 lines · 87 tokens per session scan A d32d9c88a8cf
uplift-migrator is an agent published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 1,099 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to uplift-migrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
plan
Triage, analyze, and create phased development plans. Iterate with the user until the plan is approved.
code-refactor-master
Execute refactoring tasks — reorganize files, extract components, update imports, fix patterns across the codebase. Use after a refactor-planner has created a plan.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
polyglot-architect
Cross-language API design and binding parity.