agentleFS
niksavisniksavis/basicly/.agents/skills/tier-injection/SKILL.md

tier-injection

Skill2 starsChanged 7 days agoMITView on GitHub

Installs the tier kit so a subagent runs on the model its tier names. Use when a host must pin the model of a spawn or a subagent ignores its tier.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use low only for work whose wrong answer a check catches and a rerun fixes cheaply.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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 or maximum. The kit changes that tier into the model the spawn runs on, at spawn time.

Rules

  • Check CLAUDE_CODE_SUBAGENT_MODEL first when a spawn ignores its tier. It outranks the value the hook writes, and the hook stays silent.
  • Relaunch the whole CLI process after a first install. The host does not watch a directory that did not exist at startup. /clear reloads neither hooks nor agents.
  • Remove a model pin to let the tier decide. The hook leaves a definition that pins its own model, and a spawn that names one.
  • Commit .basicly/core/models/model-map.json in the repository. A repository with no map in its own tree gets no rewrite.

What the kit is

The kit is three files in .basicly/core/kit/tier/: install_hook.py, claude_tier_hook.py and tier_resolver.py. It needs no basicly import, nothing on PATH, no third-party package and no network. Copy the three files and .basicly/core/models/model-map.json into any repository, and the kit works there.

HostResult
Claude CodeA PreToolUse hook on the Agent tool
Copilot CLINothing. Copilot selects the model of a subagent in its configuration, and the kit does not write that configuration

Install

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

A second run changes nothing. For every flag (--user, --host, --root, --interpreter, --uninstall) and the command each scope writes, read install.

Check a resolution without a spawn

python3 .basicly/core/kit/tier/tier_resolver.py --host claude --name my-agent

It exits 0 with a model and an alias, or exits 1 with the reason that nothing resolved. Other options: --definition <path>, --tier <tier>, --default-tier <tier>, --vendor <vendor>, --map <path> and --root <path>.

Behaviour to expect

  • The hook writes an alias such as opus, not a model id. The model field of the Agent tool takes an alias. The frontmatter of a definition takes a full model id.
  • A tier that the map marks unavailable resolves to nothing, never to the model of another tier.

When the repository requires tier-only dispatch

  • A dispatch declares a tier: low, medium, high or maximum. It never names a provider model id; the tier kit's model map resolves the tier.
  • Choose the tier by the cost per landed correct change: tokens, time and human interventions. A weak model's mistakes return as rework on the same change.
  • Use low only for work whose wrong answer a check catches and a rerun fixes cheaply. Start implementation from prose, decomposition, design and costly judgements at high.
  • A dispatch with no tier is a bug. It inherits the session's own model.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.