Best fit
A maintainer needs a code-review queue before a model change, or has sourced migration rules to evaluate against a reviewed deployment inventory.
Review model-version coupling in code, or compare reviewed deployments against exact, dated provider, platform and endpoint migration rules.
Prefer Gumroad? Get Model Migration Checker for $15 USD on Gumroad. Review checkout for tax or currency conversion.
Access: Agent-loaded on Agensi, not a standalone app. Downloadable access applies only where a separate download offer is linked. Package version 1.1.1.
Package requirements: Python 3.10 or newer; standard library only. A terminal, or an agent that can read SKILL.md and run local Python. For a downloadable package, extract the complete folder before use.
You get: Heuristic scanner, editable patterns, separate scoped-rule evaluator, fixtures, tests and rule-contract guidance.
Review the package licence and seller terms at checkout. An AI-agent subscription or setup service is not included.
Agensi access: In a creator test on October 17, 2026, Claude retrieved this package’s helper and required supporting files through Agensi and executed synthetic cases in its local Python sandbox. This was not Agensi-hosted execution, a complete package test, or a guarantee for other hosts. Local setup examples below apply to the separate downloadable package.
For the separately obtained downloadable package, extract the entire ZIP, keep scripts and references together, and open a terminal in the extracted skill folder. On Windows, use py -3 instead of python if needed.
python scripts/scan_model_migration.py fixtures/risky-sampleThe packaged risky fixture returns eleven findings for model IDs, coupling and review candidates. The max_tokens and functions matches are REVIEW_CANDIDATE findings, not confirmed deprecations. Exact endpoint and provider evidence are needed for the separate scoped-rule assessment.
Review findings before changing code. For the separate scoped mode, read references/scoped-rules.md and use scripts/evaluate_scoped_rules.py with your reviewed deployment and dated source rules. The package does not fetch current provider rules.
Reviewed non-secret local source for the heuristic scan; supplied deployment and dated rule records for the separate scoped evaluator. No provider calls or source authentication.
Not an automatic migration, a current provider-rules database, or proof that a parameter is deprecated or a migration is safe. Missing, linked or unreadable inputs must not be treated as a clean result.
A maintainer needs a code-review queue before a model change, or has sourced migration rules to evaluate against a reviewed deployment inventory.
Heuristic code findings, or a separate scoped rule report with APPLIES, DOES_NOT_APPLY and UNKNOWN_SCOPE decisions.
Not an automatic migration, a current provider-rules database, or proof that a parameter is deprecated or a migration is safe.
No. Heuristic patterns are editable, and scoped rules need dated sources and exact provider, platform and endpoint scope. Keep them current yourself; a matched parameter alone does not prove deprecation.
Choose your access route above and start with a reviewed example.
Get the Model Migration Checker on Agensi