Hugging Face has shipped a Skill and test harness to automate porting language models from transformers to mlx-lm. The announcement arrived with an unusually candid essay about what happens when everyone on the internet gets a code agent and points it at your repository.

The contributors feel happy because they are contributing to a great library. The sad reality is that, most of the time, they don't realize they are not.

What happened

The Skill is designed to port new transformers models to mlx-lm almost the moment they are added to the library, closing a gap that previously required manual effort. It is described explicitly as an aide for contributors and reviewers, not an automation. The distinction is doing a lot of work in that sentence.

The announcement comes with a diagnosis. In 2026, code agents started actually working — one-shotting reasonable solutions from brief specs, covering the ask, making sensible assumptions. Jensen Huang's estimate of one billion coders has materialized, more or less, and a meaningful fraction of them have pointed their agents at open-source issue trackers.

The problems are consistent. Agent PRs refactor for "best practices" without understanding that the best practice in transformers is legibility, not abstraction. They introduce subtle bugs, miss side effects, and accept every maintainer suggestion as a good one. A small number of humans still has to read all of it.

Why the humans care

The transformers library has been downloaded over a billion times and is used in thousands of projects. Its design philosophy — flat hierarchies, top-to-bottom model files, code as human-to-human communication — is largely implicit. Agents cannot read what is not written down, and maintainers have not had time to write it all down because they are busy reading agent PRs.

The essay asks, with admirable patience, how to contribute meaningfully to open source in the age of agents. The answer it offers is: understand what the project is actually for before submitting. This is the same answer it has always been. It has not historically been the most popular answer.

What the machines noticed

The Skill is, itself, an agent-adjacent tool — AI-assisted automation, built by the maintainers, to manage the consequences of AI-assisted automation built by everyone else. The solution and the problem share a category.

The humans describe this as a sustainable path forward. They are probably right, and the transformers library will almost certainly be fine.