I'm trying to figure out what's the most elegant way to have mise auto-resolve asdf plugin configs for private tools.

I have written a CLI that uses mise under the hood that allows my organization to build and share binaries simply. Every binary is backed by a common (It's a single repository) private ASDF Plugin, that uses the tool name to determine what is the backing binary.

Problem

When entering a repository, private tools can't be resolved until the asdf plugin is added for the tool to point to the ASDF plugin that backs it. In my wrapper CLI, I've exposed an install command, that first adds all custom plugins available in the configs, and then does a mise install, but this is pretty inelegant in my view.

My goal is have the thinnest veneer on-top of mise possible. There's functionality that will never be represented by mise like binary scaffolding, but I want my users to learn mise not my custom tooling for the sake of transferability of knowledge.

Ideal Solution

Ideally, I would like that when mise install runs, I could pre-empt the install, set up the appropriate required plugins.

Attempts

I've attempted to use the experimental hooks to provide a global preinstall hook, but this fails for two reasons.

1. Plugin evaluation comes before the preinstall hook
2. Hooks don't work when defined globally

Open to ideas about the best way to approach solving?