tier-injectionlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Tier Injection A subagent definition declares a portable `tier` (`low`, `medium`, `high`, `maximum`) rather than a provider model id. The kit turns that into the model the spawn actually runs on, at spawn time. Three files under `.basicly/core/kit/`, and **nothing else** — no `basicly` import, nothing on `PATH`, no third-party package, no network. Copy them plus `.basicly/core/models/model-map.json` into any repository and it works there. ## When To Use - Setting tier injection up in this repository or in one that has no harness. - A subagent ran on the wrong model though its definition declares a tier. - Deciding whether a given host can pin a spawn's model at all. ## Install ```bash python3 .basicly/core/kit/tier/install_hook.py --dry-run python3 .basicly/core/kit/tier/install_hook.py python3 .basicly/core/kit/tier/install_hook.py --user ``` Default scope is this repository's `.claude/settings.json`. `--user` widens it to every repository on the machine — safe, because the hook only answers for a directory tree that has its own committed map, but it is a deliberate opt-in rather than the default. Re-running converges: it never duplicates the hook and never touches one you wrote yourself. **The two scopes are written differently, on purpose.** The repository's file is committed and shared, so it gets a command with nothing machine-specific in it — the hook is named through