diff --git a/tests/agent/test_minimax_provider.py b/tests/agent/test_minimax_provider.py
index bed3c1166..2dd151078 100644
--- a/tests/agent/test_minimax_provider.py
+++ b/tests/agent/test_minimax_provider.py
@@ -157,11 +157,21 @@ class TestMinimaxAuxModel:
     """
 
     def test_minimax_aux_is_standard(self):
+        # Import model_tools to trigger plugin discovery so the
+        # ProviderProfile objects are registered in the providers
+        # registry before _get_aux_model_for_provider() is called.
+        # Without this, profile-based resolution can be order-dependent
+        # or fail outright in isolation (the minimax-* entries are
+        # no longer in _API_KEY_PROVIDER_AUX_MODELS_FALLBACK after the
+        # minimax-M3 default-aux-model cleanup, so the profile is
+        # the only path to a non-empty aux value).
+        import model_tools  # noqa: F401
         from agent.auxiliary_client import _get_aux_model_for_provider
         assert _get_aux_model_for_provider("minimax") == "MiniMax-M3"
         assert _get_aux_model_for_provider("minimax-cn") == "MiniMax-M3"
 
     def test_minimax_aux_not_highspeed(self):
+        import model_tools  # noqa: F401
         from agent.auxiliary_client import _get_aux_model_for_provider
         assert "highspeed" not in _get_aux_model_for_provider("minimax")
         assert "highspeed" not in _get_aux_model_for_provider("minimax-cn")
diff --git a/tests/plugins/model_providers/test_minimax_profile.py b/tests/plugins/model_providers/test_minimax_profile.py
index 495c125ce..e66b0dea8 100644
--- a/tests/plugins/model_providers/test_minimax_profile.py
+++ b/tests/plugins/model_providers/test_minimax_profile.py
@@ -42,13 +42,14 @@ def minimax_profile(request):
 class TestMinimaxAuxModelM3:
     """MiniMax profile aux model is the new frontier M3, not the stale M2.7.
 
-    The catalog top entry is ``MiniMax-M3`` (hermes_cli/models.py:298) and
-    the user-facing ``model.default`` for a Token-Plan install is M3, so
-    pinning the aux default to the same model keeps the runtime consistent
-    (same auth, same billing pool, same rate limits, no surprise 2x-cost
-    highspeed variant). M3 was released 2026-06-01 — picking it as the
-    aux default matches the forward-looking catalog order rather than the
-    pre-M3 era.
+    The catalog top entry is ``MiniMax-M3`` in
+    ``hermes_cli.models._PROVIDER_MODELS['minimax']`` and the
+    user-facing ``model.default`` for a Token-Plan install is M3,
+    so pinning the aux default to the same model keeps the runtime
+    consistent (same auth, same billing pool, same rate limits, no
+    surprise 2x-cost highspeed variant). M3 was released 2026-06-01
+    — picking it as the aux default matches the forward-looking
+    catalog order rather than the pre-M3 era.
     """
 
     @pytest.mark.parametrize(