<- all tokdocs

Claude Code Modernization Plugin: How It Proves a Rewrite Works

By , founder of Mavric and Apso

View on TikTok ->

The code-modernization plugin in Anthropic's claude-plugins-official repository points Claude at a legacy codebase and produces an understanding of it, a plan you approve, the rewritten code, and script-checked proof that the new code behaves like the old. A TikTok from Robert Ta (@therobertta_) reads its README accurately. The plugin was not new when he posted it on 14 November 2026, and the video skips a few limits on what "proof" means.

What is the Claude code-modernization plugin?

The plugin lives at plugins/code-modernization in the anthropics/claude-plugins-official repository on GitHub. Its README opens with "Point Claude at a legacy codebase and get four things":

  1. An understanding: an assessment, a dependency map, and business rules written as Given/When/Then cards with file:line citations.
  2. A plan that you must approve before anything is built.
  3. The modernized code.
  4. Proof that the new code behaves like the old, produced by a step called modernize-verify.

The README says it handles any language and any kind of move: a newer version, a rewrite in another language, or a rebuild on a new architecture. The video does not mention that scope.

Is the plugin new?

The video says "Claude Plugins Official in their repo just dropped an official code modernization plugin." The GitHub page on screen shows the last commit, by morganl-ant, as "3 weeks ago."

The commit history for the folder lists 35 commits under the date Sep 25, 2026, all by morganl-ant. The newest titles are "count failures and the machine's python, once per version" and "version 1.0.0, usage counts and a README results table." Older commits sit on further pages, so the first commit date is unknown. The plugin had been in the repository and reached version 1.0.0 before the video was posted.

How does it prove the rewrite works?

The video says the proof is "built from evidence a script can check, not from the model's opinion." The README describes several controls.

Byte comparison. Where the legacy code can run, old and new code run on the same inputs, and a script compares every byte of output. Fields that must vary, such as timestamps and generated IDs, are masked, and each masked field is listed. A commit title notes that floating-point output is compared within a declared tolerance. So "every byte" holds after the listed exceptions.

Invented inputs. The verifier invents at least ten new inputs and compares again. They cover boundaries, empty and huge inputs, unusual ordering, and malformed records when exact behavior is requested.

The canary. A deliberate one-line break must turn the tests red. This shows the test suite is capable of failing.

Checking the checker. The comparison is tested by changing one byte of an output to confirm the script catches it.

Clean re-runs. Tests are re-run from clean. A run that executed no tests, or skipped them, counts as a failure.

Critical rules. Each critical (P0) business rule must be named by a test that ran and passed. Rules backed only by skipped tests are reported as "named, not run." The video says "every critical rule is backed by a test that ran," which matches.

What verdicts does it give?

Each module gets one verdict from scripts/proof_pack.py: PROVEN, PARTLY PROVEN or NOT PROVEN. If the legacy system cannot run in your environment, the best possible verdict is PARTLY PROVEN, because there is nothing to compare against byte for byte. The video does not mention that ceiling.

What the canary does and does not show

The canary proves the tests can fail. It does not prove the tests cover what the legacy code actually does. The invented-input comparison against the running legacy system is the control aimed at that second question, which is why a legacy system that cannot run caps the verdict.

What the video does not show

The speaker reads the README aloud. There is no run of the plugin on a real codebase, no verdict output and no failure rate. He closes with "seems to be very well thought out from what I'm reading here," which is a reading, not a test. The README has a results table, according to a commit title, but the video does not cite it.

The description says this is how "most legacy rewrites go wrong without anyone noticing." Neither the video nor the README gives a source for "most."

The description links a longer YouTube video, which was not reviewed here.

Bottom line

The plugin's README matches the video: four deliverables, byte comparison of old and new output, at least ten invented inputs, a canary and a one-byte check of the comparison. The byte comparison excludes listed masked fields, and a legacy system that cannot run caps the result at PARTLY PROVEN. The plugin had 35 commits and a 1.0.0 version weeks before the video called it new.

Sources

Published November 14, 2026. Based on a TikTok by @therobertta_. Full video notes (markdown)