What they did
u/jfowers_amd, who works in AMD's AI group, spent a couple of weeks building an agent skill for hrx-loom, an experimental AMD compiler, runtime and serving stack whose kernels are written in a vector language that suits agents better than people. Given a Hugging Face GGUF model, the skill gets it running on loom-serve, optimises the kernels and reports speed against llama.cpp. The poster then pointed it at the 51 top trending LLMs that fit on a Strix Halo machine and uploaded the resulting model programs to Hugging Face. The post does not name the agent harness the skill ran in.
How it went
All 51 models ported, with tool calling, speculative decoding and image input working. The poster says the generated kernels were consistently faster than llama.cpp on Vulkan and ROCm for a range of prefill and decode measures on Strix Halo, with the data published per model. In the comments they add that one agent spent 24 hours on a single machine pushing one model further, and hit a limit in the SDK's disk streaming rather than in the kernels. One commenter noted that model was still slower than other community engines. A week later a second engineer on the team ran the skill with the pi.dev agent on Gemini 4 Neon against Inkling-2-Mini on its release day: about 4.3 hours and 490 tool calls to a package that passed every correctness gate, with decode at 44.8 tokens a second against 23.8 for llama.cpp.
Worth knowing
This is a vendor engineer promoting a v0.1.0 prerelease of their employer's tool, and the speed numbers are their own. The skill was only run on Q4_K_M quants; the poster expects other quants to work but has not tried them. Early tests of running the skill fully locally with an open model are mentioned but not reported. The skill will not count a speedup until token-level outputs match llama.cpp, which is what makes the numbers worth reading.