GitHub Repos

Week's Top GitHub Repos: OpenCut, SkillSpector, Agent-Reach, System Prompt Leaks, and More

The June 18 GitHub Hot Repos report on Heatcheck from The Next New Thing is one of the clearest agent-stack snapshots so far.

The interesting part is not only the list of repos. It is the shape of the list: marketing skills, engineering skills, open video editing, native containers, skill security, product-management workflows, agent web access, token compression, local media automation, and system prompt archaeology.

Credit where it belongs: the repo suggestions, Heatcheck report, timestamps, X references, and supporting video links come from The Next New Thing and Andrew Warner's weekly GitHub Hot Repos format. JQ AI SYSTEMS is adding the practical builder filter: what each repo does, what layer it fills, what to be careful with, and which ones I would test first.

Source Note

This post follows the June 18 report and the supplied video transcript. The report's star counts are useful as a time-stamped attention signal, not as proof that a repo is production-ready. For anything that touches credentials, cookies, local files, agent skills, or browser automation, review the code and test inside a disposable workspace first.

Main Video

Video credit: The Next New Thing. Report credit: The Next New Thing and the June 18 Heatcheck report.

Hidden Finds

The report opens with three "hidden finds." They are worth treating separately because they are less about this week's main ranking and more about where the agent ecosystem is quietly moving.

Repo Why it matters JQ AI SYSTEMS read Source
coreyhaines31/marketingskills
Marketing skills - ~33.9k stars in the report
Agent skills for conversion optimization, copywriting, SEO, analytics, and growth engineering. This is one of the most useful directions for non-engineering teams: teach the agent actual marketing procedures instead of asking for generic advice. X post
mattpocock/skills
Engineering skills - ~135k stars in the report
Small, composable, personal agent skills from Matt Pocock, positioned as skills for real engineering rather than a heavy process framework. A good reminder that the best skill packs may be small. The agent needs a few good rails, not a whole fake operating system. X post
OpenCut-app/OpenCut
Open-source video editor - ~57.1k stars in the report
A free, open-source CapCut alternative for web, desktop, and mobile, with a rewrite moving toward a Rust core, plugins, and MCP control. Very relevant for creators and agencies. If the editor becomes scriptable by agents, video production gets a cleaner local/open-source path. X post

The most useful idea here is skills for business functions. Coding agents got the first big wave of skill packs, but marketing, product, sales, finance, and operations are the next obvious targets.

Main Report Picks

Rank Repo Why it matters JQ AI SYSTEMS read
01 apple/container
Native containers on Mac - 38.2k stars in the report
Apple's Swift-based CLI runs Linux containers as lightweight VMs on Apple silicon with OCI-compatible images. A strong local-dev and agent-sandbox signal. It is especially interesting for Mac builders who want isolation without the weight of Docker Desktop.
Related X source
02 NVIDIA/SkillSpector
Skill security scanner - 3.9k stars in the report
Scans AI agent skills for risky behavior, malicious patterns, and security problems before installation. This may be the most important repo in the set. Skills are becoming executable work instructions, so skill review needs tooling.
Related X source
03 addyosmani/agent-skills
Engineering workflow skills - 7.3k stars in the report
Production-grade coding-agent skills around specification, planning, building, testing, reviewing, simplifying, and shipping. Useful because it slows the agent down and gives non-experts a real engineering loop: define, plan, build, verify, review, ship.
Related X source
04 phuryn/pm-skills
Product management skills - 15.2k stars in the report
A product-management skills marketplace with commands and workflows for discovery, positioning, requirements, and launch work. Good for turning messy product thinking into repeatable agent procedures. Still review every template against your actual business.
05 iptv-org/iptv
Public IPTV index - 114k stars in the report
A large collection of publicly available IPTV channels that can be used with players such as VLC or PotPlayer. Interesting as an open media index, but respect rights, regional rules, and source legitimacy. Do not treat "available" as the same thing as "safe for every use."
Related X source
06 Panniantong/Agent-Reach
Internet reach for agents - 21.2k stars in the report
A CLI layer that helps agents access public web sources such as YouTube, X, Reddit, GitHub, RSS, LinkedIn, Bilibili, and more. Powerful for research agents, but high-risk if you hand it cookies, credentials, or unattended account access. Test it with low-stakes sources first.
07 chopratejas/headroom
Token reduction proxy - 19.2k stars in the report
Compresses tool outputs, logs, files, and RAG chunks before they hit the model, aiming to cut token usage in noisy agent workflows. Best tested where tools are verbose: file search, logs, large JSON, and repeated tool output. Measure answer quality, not only token savings.
Related X source
08 mvanhorn/last30days-skill
Fresh research skill - 29.2k stars in the report
Researches fresh activity across GitHub, YouTube, Hacker News, X, Polymarket, Reddit, and the web, then synthesizes a grounded brief. Great fit for weekly idea packs and market scans. The key is to keep citations and distinguish popularity from truth.
Related X source
09 music-assistant/server
Self-hosted music automation - 8.5k stars in the report
A free, open-source media library manager that connects streaming services, local files, and speakers in a smart-home style setup. Not an AI-agent repo, but very relevant to local-first automation: self-hosted control, integrations, and a real user interface.
10 asgeirtj/system_prompts_leaks
System prompt study - 84.9k stars in the report
A regularly updated archive of extracted system prompts from major AI products and agents. Useful for prompt literacy. Study how products structure roles, refusals, tools, and style. Do not copy blindly or treat leaked prompts as policy templates.
Related X source

Zapier MCP

The video also includes Zapier MCP as the sponsor/tooling insert. I would not count it as one of the GitHub repos, but it belongs in the same stack map.

The practical value is permission design. Instead of giving an agent full access to Gmail, Notion, Calendar, or a CRM, Zapier MCP lets you expose a controlled toolbox of actions. For small teams, that is often the difference between "cool demo" and "this can touch real work."

Demo Videos From Heatcheck

The Heatcheck page preserved supporting videos for several picks. I am embedding those here so the post has the same practical "show me it working" layer as the source report.

NVIDIA/SkillSpector

AI LABS: installing and running SkillSpector

addyosmani/agent-skills

Bitwise AI: doubt-driven development with agent-skills

iptv-org/iptv

Kernel Exploit: using the iptv-org playlist in PotPlayer

chopratejas/headroom

Better Stack: Headroom explainer and demo

music-assistant/server

Everything Smart Home: Music Assistant with Home Assistant

asgeirtj/system_prompts_leaks

Bitwise AI: system prompt leaks across AI agents

The Pattern This Week

This is the first weekly repo list where the agent-skill layer feels bigger than the model layer.

marketingskills, mattpocock/skills, agent-skills, pm-skills, and last30days-skill are all saying the same thing in different languages: agents need reusable procedures. The user should not have to re-explain how to write a PRD, run a research scan, structure an engineering plan, or audit a landing page every time.

SkillSpector is the matching safety layer. The moment skills become installable, they become supply-chain objects. A skill can tell an agent what to read, what tools to call, what commands to run, and what to ignore. That is powerful. It is also a security surface.

Agent-Reach, headroom, and apple/container fill the infrastructure gaps: web reach, cheaper context, and safer local execution. OpenCut and music-assistant/server show the local/open-source automation side. system_prompts_leaks is the learning layer: builders want to see how serious AI products actually instruct their agents.

JQ AI SYSTEMS Top 10 For This Week

If I were advising a builder this week, I would not rank by GitHub stars. I would rank by workflow leverage, security value, and usefulness for real small-team systems.

  1. NVIDIA/SkillSpector: Best risk-control pick. If skills are becoming packages, scanning those packages matters.
  2. OpenCut-app/OpenCut: Best creator tooling pick. Open, scriptable video editing is exactly where agents can become useful.
  3. coreyhaines31/marketingskills: Best business-side skill pack. Marketing workflows are where many founders need agent leverage first.
  4. addyosmani/agent-skills: Best engineering-process pick. It teaches the agent to work in smaller, reviewable steps.
  5. apple/container: Best infrastructure signal. Better local isolation helps agents run work without touching the whole machine.
  6. mvanhorn/last30days-skill: Best research-workflow pick. It turns recency into a repeatable agent routine.
  7. Panniantong/Agent-Reach: Best public-web access idea, but also one of the biggest permission-review risks.
  8. chopratejas/headroom: Best cost and context-control idea for verbose tool output.
  9. phuryn/pm-skills: Best PM workflow package if your team needs better requirements, positioning, and launch structure.
  10. asgeirtj/system_prompts_leaks: Best prompt-literacy resource, as long as it is used for study rather than blind copying.

My top three are SkillSpector, OpenCut, and marketingskills. SkillSpector protects the new skill supply chain. OpenCut points to open, agent-scriptable creative work. marketingskills translates agent workflows into a business function that founders already pay for.

Builder Checklist

  • Pick the missing layer. Marketing, engineering process, PM workflow, skill security, browser reach, token control, local containers, media automation, or prompt literacy.
  • Check permissions before installation. Any repo that touches cookies, browsers, tools, accounts, files, or shell commands needs review.
  • Use a disposable workspace first. Agent skills and tool wrappers should be tested with fake data before client or business data.
  • Look for working examples. Stars are not enough. Prefer demos, docs, tests, active issues, and real usage notes.
  • Review prompt packs like code. A skill can change how an agent thinks, what it ignores, and which tool calls it prefers.
  • Measure the workflow. Did it save time, reduce tokens, improve output quality, or make review easier?
  • Package what works. If one repo improves a repeated workflow, turn your setup into a documented skill or SOP so the gain compounds.

The clean takeaway: agent work is becoming installable. That is exciting, but it changes the job. The builder now has to choose the right workflow package, scan it, scope it, test it, and then fold it into a system with memory, logs, and review.


Sources And Links

Common questions

Who selected the repos in this June 18 roundup?
The repo suggestions come from The Next New Thing and its June 18, 2026 Heatcheck report. JQ AI SYSTEMS adds the builder/operator interpretation and a separate recommended top 10 at the end.
Why does this roundup include both skills and security tools?
Because agent skills are becoming installable software. If teams install marketing, PM, coding, or research skills, they also need scanners like SkillSpector and review habits before giving those skills real tool access.
Which repo is the most practical first install?
For most builders, NVIDIA SkillSpector or Addy Osmani's agent-skills are the safest first tests: one improves security review, the other improves coding-agent process without needing credentials.
Should I copy leaked system prompts from system_prompts_leaks?
No. Treat leaked prompts as education about structure, constraints, and workflow design. Do not blindly copy proprietary prompts or assume that a leaked prompt is the right policy for your own agent.
What is the biggest JQ AI SYSTEMS takeaway?
The agent stack is moving from model choice to workflow packaging: skills, PM playbooks, marketing procedures, security scanning, web reach, token compression, and prompt literacy.
Share
X LinkedIn Reddit
Build Yours

Want a system
like this one?

Book a free 30-minute call. We map your situation, identify the highest-impact automation, and figure out if we are a fit.

Book Free 30-min Call