GitHub radar
Top 5 GitHub Repos This Week
This week was dominated by agent tooling — two repos tackle the age-old problem of making AI reach the physical world (your phone, your text). The surprise was a C repo racing to the bottom of CPU performance and a designer who shipped an entire immersive Three.js experience as a single HTML file.
I installed this skill into my agent and the difference was immediate — outputs stopped sounding like a summary machine. The project takes a clever approach: instead of banning specific phrases, it detects underlying structural patterns — 'report voice', uniform sentence lengths, over-explaining the obvious. Version 1.1.0 moved to pattern-based detection rather than character-string bans. The lite version fits in ~2,000 characters, so it works directly in a chat window without any setup.
Why a vibe-coder should care
If you're building any writing-assistant pipeline, this is the clearest thinking I've seen on the problem: detect structure, not strings.
Paired my iPhone with macOS Mirroring and ran this in about fifteen minutes — no jailbreak, no developer account required. The core idea is elegant: ~500 lines of Python capture the mirrored window as screenshots, Vision OCR finds tap targets, then HID-level events send input back to the device. The README describes it as 'the poor man's DOM' which is exactly right. It's stateless — no background daemon, each run is a clean slate.
Why a vibe-coder should care
Phone control for AI agents without any Apple developer infrastructure — a serious unlock for automation workflows that need a mobile layer.
I spent an embarrassing amount of time reading this. xoreaxeaxeax — the same author behind ropeme and sandsifter — catalogues x86 instructions ranked by worst-case execution latency, the exact opposite of what performance guides normally teach. The top entry is fxrstor64 with PCIe starvation: ~198 billion cycles per instruction. They managed to make rdrand take 5,579 cycles by depleting the hardware entropy pool — a detail I never would have thought to look for.
Why a vibe-coder should care
Knowing the floor of CPU performance is as useful as knowing the ceiling — these patterns define microarchitectural attack surfaces and real-world denial-of-service vectors.
MengTo (Design+Code) dropped a single HTML file that runs an interactive night walk through a Kyoto mountain temple — no build step, no npm install. I cloned it and opened index.html immediately. The WebGL camera moves as you scroll through five chapters, layering procedural fog, rain, lanterns, and falling leaves over pre-rendered scene plates. The no-build constraint is a deliberate design choice: the whole experience is one file you can study, copy, and remix.
Why a vibe-coder should care
A no-build Three.js demo that packs this much atmosphere into one file is worth studying before you reach for another framework.
JD's research team open-sourced their real-time video editor: a 16B multimodal diffusion transformer that edits frames as they stream in, hitting 30.19 FPS at 720×1280 resolution end-to-end. The README shows five demo categories — style transfer, subject replacement, background changes — all running on live input without buffering the full clip first. I was skeptical about 'real-time' claims, but 30 FPS at 720p from a 16B model is genuinely impressive.
Why a vibe-coder should care
The streaming architecture — no full-clip buffering required — is what makes this practically deployable, not just another research demo.
▌ More finds