The AI Radar Kit

You'll get a personal briefing: the 3 AI launches from this week that matter for your work, why they matter, and what to do next. No setup.

1. Open prompts/what-matters-prompt.md and copy the prompt.
2. Fill the 3 lines under ABOUT ME (what you do, who you serve, what you want).
3. Under THE LINKS, paste this week's list:

1. affaan-m/ECC — https://github.com/affaan-m/ECC — Performance system for AI coding agents: skills, memory, security. +897 stars in a day.
2. Panniantong/Agent-Reach — https://github.com/Panniantong/Agent-Reach — Lets your AI agent read and search X, Reddit, YouTube, GitHub. +1,696 stars in a day.
3. DietrichGebert/ponytail — https://github.com/DietrichGebert/ponytail — Makes your AI coding agent write less, simpler code. #1 on GitHub Trending.
4. heygen-com/hyperframes — https://github.com/heygen-com/hyperframes — Write HTML, render video. Built for AI agents. +580 stars in a day.
5. KKKKhazix/AIHOT — https://github.com/KKKKhazix/AIHOT — Open-source framework for a self-running industry news site with AI-written daily reports. ~1,073 stars/day.
6. mksglu/context-mode — https://github.com/mksglu/context-mode — Cuts how much of your AI coding agent's memory gets eaten by tool output.
7. Louis-CFM/coucou — https://github.com/Louis-CFM/coucou — A tiny app in your Mac's notch that watches your coding agents.
8. mvschwarz/openrig — https://github.com/mvschwarz/openrig — Run persistent teams of Claude Code / Codex agents with roles.
9. NVIDIA/OpenShell — https://github.com/NVIDIA/OpenShell — NVIDIA's sandbox runtime that limits what AI agents can touch.
10. edenfunf/reelmimic — https://github.com/edenfunf/reelmimic — Show it a video you love; AI agents make a new one in the same style.
11. MAI-Transcribe-2-Streaming — https://the-decoder.com/microsoft-ai-releases-new-transcription-and-text-to-speech-models-for-voice-agents/ — Microsoft's new real-time speech-to-text model, 60 languages.
12. Meta Muse gadget SDK — https://www.theverge.com/tech/1004330/meta-muse-ai-gadgets-home-link — Meta open-sourced code to build your own Muse AI gadgets.

4. Send. In under a minute you have a briefing written for you, not for "everyone into AI".

Next week, paste your own radar's digest instead. That's what chapter 4 builds.

How these were picked. My radar (Shipyard OS) scanned GitHub, Hacker News, Reddit, Hugging Face, 26 feeds and 80+ AI creators between September 27 and October 3, 2026, and scored every item on velocity, relevance, freshness and source trust (chapter 3). I took the top of the list, removed drama and duplicates, and checked every entry against its source on October 4, 2026: the repo exists, the description is accurate, the install command is the one in the official README.

How to read the verdicts.

• SHIP: worth 10 minutes of your time this week.
• WATCH: real, but early, niche or heavy to set up. Bookmark it.
• SKIP: I'd skip it unless you're the exact person it's built for.

Star counts are a snapshot from October 3–4, 2026. They move fast.

1 · Ponytail — make your AI coding agent write less code

Link: https://github.com/DietrichGebert/ponytail · MIT license What it does: A plugin/skill set that makes your coding agent climb a "laziness ladder" before writing anything: does this need to exist? Is it already in the codebase? Does the standard library do it? Only then does it write the minimum that works. It keeps validation, error handling, security and accessibility. Who it's for: Anyone using Claude Code, Codex, Cursor, Gemini CLI or similar who's tired of 300-line answers to 10-line problems. The signal: #1 on GitHub Trending, +1,281 stars in a day, 153K stars total. Try it in 2 minutes (Claude Code): send these as two separate messages:

/plugin marketplace add DietrichGebert/ponytail

/plugin install ponytail@ponytail

Then ask your agent for something it usually over-builds ("add a date picker to this form") and compare. Dan's verdict: SHIP. The authors' own benchmark reports ~54% less code on average across 12 tasks (up to 94% where agents over-build). That's their number, not mine, and they openly corrected an earlier, rosier claim. That honesty is why I'd try it. The plugin runs small Node.js hooks, so node must be on your PATH.

2 · Agent Reach — let your AI agent read X, Reddit, YouTube and GitHub

Link: https://github.com/Panniantong/Agent-Reach · MIT · English README at docs/README_en.md What it does: One installer that gives your agent working access to platforms that normally block it: any web page as clean Markdown, YouTube subtitles and search, GitHub, RSS, X (with your cookie), Reddit (via your browser session), plus Chinese platforms. It picks a backend per platform and switches when one breaks. It includes agent-reach doctor to show what works. Who it's for: Researchers, marketers and builders who want their agent to "go read what people are saying about X". The signal: +1,696 stars in a day (the fastest repo on the list), ~90K total. Try it in 2 minutes: paste this into Claude Code (or any agent that can run commands):

Install Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md

By default the install only checks your environment; it changes your system only with --system. Dan's verdict: SHIP, carefully. The zero-config parts (web pages, YouTube, GitHub, RSS) are the 2-minute win. X and Reddit need cookies from a logged-in browser, so use a secondary account and read what you're granting. Note its own README says Reddit has "no zero-config path" anymore. That matches what I found building the radar (chapter 4).

3 · HyperFrames — write HTML, render video

Link: https://github.com/heygen-com/hyperframes · Apache-2.0 · by HeyGen What it does: An open-source framework that turns HTML, CSS and animations into deterministic MP4 videos. You (or your AI agent) write a web page; it renders frame-perfect video. Ships as Claude Code skills plus a CLI with ready-made blocks (transitions, social overlays, animated charts). Who it's for: Creators who want motion graphics, title cards or animated captions without After Effects, especially if you already let Claude write code for you. The signal: +580 stars in a day, 56K total. A Reddit post titled "Claude made us a launch video entirely in code" hit r/ClaudeAI's top list the same week. Code-made video is having a moment. Try it in 2 minutes (needs Node.js):

npx hyperframes init my-video
cd my-video
npx hyperframes preview

Or in Claude Code: claude plugin marketplace add heygen-com/hyperframes, then claude plugin install hyperframes@hyperframes, then ask for "a 10-second title card for my channel". Dan's verdict: SHIP if you make short-form content. The learning curve is "can you describe what you want". The limit: it's for graphics and text motion, not for editing your camera footage.

4 · context-mode — stop tool output from eating your agent's memory

Link: https://github.com/mksglu/context-mode · Elastic License 2.0 (free to use; you can't resell it as a hosted service) What it does: An MCP server + hooks that keep raw tool output (web snapshots, logs, long file reads) out of your agent's context window, and track your session in a local SQLite database so the agent picks up where it left off after the conversation compacts. Supports Claude Code and 16 other platforms. Who it's for: People who run long Claude Code sessions and watch them get "forgetful" after 30 minutes. The signal: +256 stars in a day, 25K total, steady for weeks. Try it in 2 minutes (Claude Code):

/plugin marketplace add mksglu/context-mode

/plugin install context-mode@context-mode

MCP-only alternative: claude mcp add context-mode -- npx -y context-mode Dan's verdict: SHIP for heavy agent users. The README's "315 KB becomes 5.4 KB" is their best case, so expect less on normal sessions. Skip it if you mostly chat with AI rather than run agents.

5 · AIHOT — the open-source "AI news site that writes itself"

Link: https://github.com/KKKKhazix/AIHOT · MIT · live demo: https://aihot.news What it does: The full engine behind a Chinese AI-news site: collects from many sources, has an LLM pre-screen and score each item twice, writes headlines and summaries, groups the same story from different outlets into one "event", ranks events by how many independent sources cover them, and publishes a daily report at 08:00 plus weekly and monthly roundups. Who it's for: Anyone who wants to run a niche news site or newsletter (legal AI, HR tech, crypto…) on autopilot. The signal: ~1,073 stars/day since it was created on September 28; 5.4K stars in under a week. Try it in 2 minutes: open https://aihot.news and look at how it groups stories into events. To run your own you need Docker and an OpenAI-compatible API key:

git clone https://github.com/KKKKhazix/AIHOT.git myhot && cd myhot
node scripts/init-env.ts --llm-key <YOUR_KEY>
docker compose up -d --build

Dan's verdict: WATCH. It's the most complete open-source radar I've seen this year, and its "count independent sources, not articles" rule is exactly what the kit's script does (chapter 3). But the README, UI and prompts are in Chinese, and it needs a server. If you want the 20-minute version, use radar/ in this kit.

6 · Coucou — a tiny friend in your notch that watches your agents

Link: https://github.com/Louis-CFM/coucou · MIT What it does: A small macOS app that lives in the notch (top of the screen on Windows/Linux) and shows what your coding agents are doing: live Claude Code sessions, permission requests you can answer from the notch, plan usage, diffs and pull requests. Supports Claude Code, Codex, Cursor, Gemini CLI and more. Who it's for: Mac users who run agents in the background and keep missing "waiting for your approval" prompts. The signal: +531 stars/day since its first release on September 27; it shipped six versions in its first week (v0.1.5 on October 4). Try it in 2 minutes: download Coucou.zip from the Releases page, move it to Applications, open it, then click Install hooks in its settings. It backs up ~/.claude/settings.json and shows you the diff before writing. Dan's verdict: SHIP if you're on a Mac and run Claude Code daily; SKIP otherwise. Windows installer is paused (Microsoft Defender false positive under review, per the README); Linux is a beta.

7 · OpenRig — persistent teams of AI agents with roles

Link: https://github.com/mvschwarz/openrig · Apache-2.0 What it does: Turns Claude Code and/or Codex sessions into a standing team: an "owner" agent does the work, a "checker" agent reviews it, they share context and keep their roles across sessions. Runs in tmux on macOS or Linux. Who it's for: Developers already comfortable with Claude Code or Codex who want a second agent reviewing the first one's work. The signal: +683 stars in a day, 4.6K total, 15th on GitHub Trending. Try it in 2 minutes (safe preview, changes nothing):

npm install -g @openrig/cli
rig setup --dry-run

Dan's verdict: WATCH. The idea (no agent grades its own work) is right. But it needs Node 22/24 and tmux, writes provider hooks and permission settings, and native Windows isn't supported. Read "what OpenRig changes on your machine" in the README before the real setup.

8 · NVIDIA OpenShell — a sandbox that limits what your AI agents can touch

Link: https://github.com/NVIDIA/OpenShell · Apache-2.0 · docs: https://docs.nvidia.com/openshell/latest/ What it does: Runs each agent in an isolated sandbox. You write a policy (which files, which websites, which APIs); OpenShell enforces it on every file access and network call. Agents never see your real credentials: they're added only to requests going to approved endpoints. Before a policy change, it flags risky new access for human review. Who it's for: Anyone giving an agent real API keys, a company laptop or a production server. The signal: +594 stars in a day, 14.7K total. Try it in 2 minutes (Linux, Apple Silicon Mac, or WSL 2; needs Docker, Podman or host virtualization):

curl -LsSf https://raw.githubusercontent.com/NVIDIA/OpenShell/main/install.sh | sh
openshell sandbox create --name demo

Dan's verdict: WATCH for most people, SHIP if you run agents with access to money, customer data or production. It collects anonymous usage telemetry by default; turn it off with OPENSHELL_TELEMETRY_ENABLED=false.

9 · ReelMimic — show it a video you love, get a new one in the same style

Link: https://github.com/edenfunf/reelmimic · MIT What it does: Breaks down a reference video (shot lengths, BPM, transitions, colors, framing), proposes a storyboard you approve, then splits production across up to 6 AI agents, with every shot reviewed by a different agent. Runs on your computer with your own Claude Code or Codex. It learns the style; it doesn't copy the original footage. Who it's for: Creators who want animated 2D content (motion graphics, watercolor, pixel art, paper cut-out…) in a style they've seen work. The signal: ~210 stars/day since September 28. It's built on HyperFrames (#3), which is a second signal: tools are stacking on it. Try it in 2 minutes (setup only):

git clone https://github.com/edenfunf/reelmimic.git && cd reelmimic
./install.sh && ./start.sh

Then open http://localhost:4318 and drop in a reference to see the breakdown. Needs Node 22.18+, Python 3.10+, FFmpeg and Chrome. Dan's verdict: WATCH. The README says a 30–60 second video takes 1–3.5 hours after you approve the plan, and it's 2D only. Impressive, not yet a daily tool.

10 · Microsoft MAI-Transcribe-2-Streaming — real-time speech-to-text, 60 languages

Source: The Decoder, October 2, 2026 What it does: Microsoft AI's first real-time transcription model. First partial results in about 100 ms, 60 languages, ranked first for accuracy on Artificial Analysis's streaming leaderboard at launch. Released with MAI-Voice-2.1 (text-to-speech with voice cloning). Who it's for: Anyone building voice agents, live captions, or call and meeting tools. The signal: Covered by The Decoder and MarkTechPost within hours of release; big-lab launch. Try it in 2 minutes: it's available in Microsoft Foundry and Microsoft's MAI Playground (free to test with a Microsoft account). Search "MAI Playground", sign in, and speak into the transcription demo. Dan's verdict: WATCH unless you're building voice products, then SHIP a test this week. Intro pricing is $0.54 per hour of audio through the end of the year, per The Decoder. Check Microsoft's pricing page before you build a business case on it.

Also on the radar this week (one line each)

• affaan-m/ECC (https://github.com/affaan-m/ECC): "agent harness performance system" with skills, memory and security for Claude Code, Codex, Cursor. 272K stars, +897/day. Huge, but a lot to absorb. WATCH.
• mattpocock/skills (https://github.com/mattpocock/skills) and obra/superpowers (https://github.com/obra/superpowers): skill libraries for coding agents, both trending again. The skills wave isn't slowing.
• feder-cr/dots (https://github.com/feder-cr/dots): open-source AI agent with its own browser. 2.6K stars in 5 days.
• Meta Muse gadget SDK (https://github.com/facebookincubator/muse-gadget-sdk): build your own hardware gadget around Meta's Muse agent (e-ink display, HDMI stick). Fun weekend project.
• OpenAI's GPT-6 model guide (https://openai.com/index/practical-guide-building-gpt-6): official guide to choosing GPT-6 models and reasoning effort. Read it if you build on OpenAI.

Skipped on purpose: the drama story of the week (an OpenAI safety lead quitting) and a viral "uncensored" home-PC model. Both were loud on Reddit and Hacker News. Neither gives you anything to use today. The radar's noise filter dropped them, and chapter 3 explains how.

My radar also tracks AI creators on YouTube and flags outliers: videos that pull far more views than that creator's median video. An outlier score of 5× means five times their typical views. Same creator, same audience, same week: the only thing that changed is the format, so outliers tell you what the market wants right now.

These are the three patterns that kept showing up (views as captured by the radar between July and October 2026):

Format 1: The day-one test, with a number

What it is: a hands-on test of something brand new, with a specific count in the title (20 examples, 100 hours, 12 use cases). Why it works: two desires at once. "Don't fall behind" (it's new) and "don't waste my time" (someone tested it for me). The number is proof of effort and tells the viewer exactly what they get. It only works in the first days after a launch, which is why a radar matters: you need to know on day one. Your short-form version: "I tested [new thing] on [N] real tasks. Here are the 3 that worked." Show 3, link the rest.

Format 2: Copy the expert's workflow

What it is: someone with clear authority (a known engineer, an ex-NASA dev, Google) shows their actual setup, and the title tells you to copy it. Why it works: borrowed credibility plus the shortest path to the result. The viewer doesn't want to learn agentic engineering; they want to have a setup that works. "Just copy him" removes the effort. David Ondrej has four videos on this list with the same skeleton. When a format works, repeat it with a new expert. Your short-form version: "This is how [credible person] uses [tool]. Steal it." Show the 3 settings or the one file that matters.

Format 3: Compressed mastery

What it is: a huge input (1,000 hours, a whole tool, "every size") squeezed into a small, exact time. Why it works: it's a price reduction. The viewer "buys" 1,000 hours of someone else's learning for 15 minutes of their own. The exact minute count makes it believable. Tina Huang uses the "[Topic] in [N] Minutes" title three times in this list, each time at 3× or more. Your short-form version: "[N] hours of [skill] in 45 seconds." Three rules, one on-screen example each.

The pattern under all three: none of these titles lead with the tool's features. They lead with effort saved (tested for you, copy him, in 15 minutes). Same lesson as the scoring formula: usable beats impressive.

Knowing first is only an advantage if you publish first. Here's the 15-minute loop I use.

The 15-minute timer

Hooks by awareness stage

How much does your viewer already know? Pick the stage, then the formula. (This is Eugene Schwartz's awareness scale, applied to AI content. Cold feeds = stages 3–5.)

Sophistication check: "5 AI tools you need" is dead; everyone's seen 500 of them. When the claim is tired, say how ("My radar flagged this at 6 a.m. Here's why it's spreading.") or speak to identity ("Builders don't wait for the newsletter.").

Script template 1: THE FIND (30 seconds, cold audience)

HOOK (0-2s)      [Stage 3-4 hook: pain or desire, NOT the tool name]
                 ON SCREEN: [same promise, ≤8 words]
YOU (2-5s)       "If you [specific situation], this is for you."
SHOW (5-18s)     [Screen recording: the result happening. Narrate what we see, one sentence per cut.]
PROOF (18-23s)   "It's free, open source, and [the one number: +1,281 stars in a day / #1 on GitHub]."
CTA (23-30s)     "Comment [WORD] and I'll send you the link plus 9 more from this week."

Filled example (Ponytail):

"Your AI writes 300 lines for a 10-line fix?" / "If you code with Claude or Cursor, this is for you." / [recording: same prompt, before and after the plugin, the diff shrinking] "Same request. Before: a new library and a wrapper. After: one line." / "It hit #1 on GitHub this week. Free." / "Comment SHIP and I'll send you the install plus 9 more."

Script template 2: THE VERDICT (35 seconds, warm audience)

HOOK (0-2s)      "I tested [tool] so you don't have to."  OR  "[Tool] is everywhere. Here's the truth."
GOOD (2-14s)     "What's good: [specific result you got, with a number or a visible output]."
BAD (14-22s)     "What's not: [one honest limit: setup time, platform, price, quality]."
WHO (22-28s)     "Use it if you [X]. Skip it if you [Y]."
VERDICT (28-35s) "My verdict: [SHIP / SKIP / WATCH]. Follow, tomorrow's test is already in the queue."

Admitting the limit is what makes the "good" believable. ReelMimic is a perfect verdict video: stunning output, 1–3.5 hours per clip. Say both.

Script template 3: THE MECHANISM (40 seconds, audience tired of tool lists)

HOOK (0-3s)      "My AI scans [400+] new AI launches every day. This morning it flagged one thing."
SIGNAL (3-12s)   "[Tool] went from 0 to [N] stars in [days]. [N] sources covered it in 24 hours."
WHY (12-25s)     "Here's why it's spreading: [the one change it makes for the viewer]."
SO WHAT (25-33s) "What it means for you: [concrete action or consequence]."
CTA (33-40s)     "Want the radar? Comment [WORD]. It's free and you can build it in 20 minutes."

This one sells you as the source, not just the tool. It's the format behind my launch reel.

Before you post: 5 checks

1. One idea, one CTA?
2. Does the hook start from the viewer's problem or desire, not the tool's name?
3. Is every number from the source (stars, price, benchmark)? No invented stats.
4. Did you say one honest limit?
5. Can someone understand it with the sound off? (Captions + on-screen hook.)