Fresh Commits 02: One Launch Grew an Entire Plugin Economy in 72 Hours

Fresh Commits is a weekly GitHub roundup for AI agent tooling, ranked by stars gained per day rather than total stars. Every figure comes from the GitHub API and passes a verification check before publication. This week is unusual: seven of the eight picks are plugins, desktops, or presets for DeepSeek Harness, a runtime that did not exist on Tuesday. The eighth comes from the creator of Cycle.js. The issue closes by returning to last week’s eight picks with one week of data attached. Two are still climbing hard, one of them up 539%. Three stalled completely, including the pick we led with. Three high-velocity repos got cut this week on licensing alone, with the reasons printed for each. Six of the eight picks ship with Chinese-language documentation only. Best for developers who want tools early. Not ideal for anyone wanting finished software.

So DeepSeek published its agent runtime on Wednesday morning. By Sunday there was a plugin marketplace, four competing desktop clients, a reasoning-mode router, an anime search plugin, plus a preset that fixes bash on Windows.

None of those existed four days ago.

Seven of this week’s eight picks plug into the same runtime. That is not a curation choice. It is what the scan returned, because almost nothing else moved.

Then at the bottom, the part that makes this a series rather than a list: last week’s eight, one week later, with the numbers.

How These Get Picked

Firstly, candidates come out of the GitHub API filtered to AI, agent, plus developer tooling, then ranked on stars gained per day since creation. Each one goes through a check covering age, license, staleness, plus the issue-to-star ratio.

Secondly, a ceiling at 20,000 stars keeps established projects out. DeepSeek Harness itself sits at over 113,000 now, so the runtime is excluded while everything built on top qualifies.

Finally, license gets checked properly. Three high-velocity repos got cut this week purely on that, which is covered at the bottom.

One repo per week gets installed and tested properly. That still has not started, so this issue runs on documentation plus verified API data. Saying so plainly rather than implying otherwise.

1. dsh-market

550 stars · 275 a day · 2 days old · MIT · TypeScript dsh-market/dsh-market

A plugin marketplace that runs inside DeepSeek Harness. Browse, search, one-click install.

Notably, somebody built an app store for a runtime that was three days old. There is a live site at dshmarket.com, 47 forks, plus 20 open issues, which for a two-day-old project means people are using it hard enough to break it.

The speed here is the interesting part rather than the code. DSH shipped with a dsh-plugin topic tag for discoverability and nothing else. Within 48 hours somebody had built the discovery layer the platform lacked. That is the pattern every successful platform follows, compressed from years into a weekend.

2. dsh-router-standard

258 stars · 129 a day · 2 days old · MIT · JavaScript yjh051108/dsh-router-standard

A task-aware reasoning-mode router with three measured behaviour bands: spec, mixed, plus reasoning.

The premise, essentially, is that different tasks want different amounts of thinking, so routing between modes automatically beats picking one and living with it. Twenty-seven open issues against 258 stars is the highest ratio in this issue by some distance, which reads as heavy real use rather than neglect.

The same author also shipped dsh-routing-suite at 1,582 stars a day, which carries no license file. This one has MIT, so this one is the pick.

3. Bigfish

236 stars · 118 a day · 2 days old · MIT · JavaScript turtle2209/Bigfish

A third-party DSH desktop client with the Node runtime bundled in. Double-click and it runs.

It also ships a desktop pet, incidentally.

That detail matters more than it sounds. DSH launched with a web interface at 127.0.0.1:3080 and nothing else, which is fine for developers and hostile to everybody else. Four separate desktop clients appeared within 72 hours. This one added a cartoon mascot because somebody decided the tool should be pleasant.

Nobody at DeepSeek planned that.

4. multi-agent-discuss

202 stars · 101 a day · 2 days old · MIT · TypeScript sjc88661/multi-agent-discuss

No description at all, oddly. Two hundred stars, 23 forks, zero explanation.

The name is the entire documentation: multiple agents, discussing. Given DSH treats the agent loop plus scheduling as swappable plugins, a discussion layer between agents is exactly the kind of thing the architecture invites.

It echoes something we covered in issue 01, where a tmux configuration let Claude Code prompt Codex in the next pane. Agent-to-agent messaging keeps arriving from unrelated directions, which usually means the idea is correct and nobody has found the right shape yet.

Included with a caveat: a repo this popular with no README is either a private project that leaked attention or something whose author expects the name to be self-explanatory.

5. deepseek-harness-studio

146 stars · 146 a day · 1 day old · MIT · TypeScript fufankeji/deepseek-harness-studio

A zero-code desktop for DSH on Windows and macOS. One-click launch, built-in plugin discovery, trending plugin recommendations, one-click install and management, plus AI-driven suggestions.

Certainly the highest velocity of the one-day-old picks. It is also the second discovery layer on this list, which tells you what the ecosystem is missing most: not capability, but a way to find things.

Backed by a company site at beyondata.com, which puts it in a different category from the weekend projects around it.

6. anime-find

123 stars · 123 a day · 1 day old · MIT · TypeScript cocofhu/anime-find

A DSH plugin that searches for anime across multiple sources inside the chat, displays Bangumi ratings and details as cards, then copies magnet links.

This one is here deliberately, though. Every other pick is infrastructure. This is somebody using an agent runtime to find cartoons, which is the clearest possible signal that a platform has escaped its intended audience.

Platforms do not become platforms when serious people build serious tools on them. They become platforms when somebody builds something frivolous, well, in a weekend. Thirteen forks in a day.

7. dsh-gitbash-preset

121 stars · 121 a day · 1 day old · MIT · JavaScript liceses/dsh-gitbash-preset

Maps the bash calls in DSH’s Minimal mode onto Git for Windows, installable as an agent preset.

Ultimately the least glamorous entry, plus arguably the most useful. DSH’s Minimal mode assumes a working bash, which Windows does not have. This makes it work.

Zero forks, zero issues, 121 stars in a day. People are starring it because they hit the problem, not because they read the code.

8. microskills

70 stars · 70 a day · 1 day old · MIT staltz/microskills

Modular prompts, used daily, by André Staltz.

Previously he created Cycle.js plus Manyverse and has been building in public for over a decade. That matters here, because a prompt collection from an anonymous account is noise while a prompt collection from somebody with fifteen years of shipped software is a look at how a serious engineer actually works.

Lowest star count in this issue. One fork. Included because the author’s track record is the signal rather than the metrics.

Last Week’s Eight, One Week Later

This is the section nobody else publishes. Every repo from issue 01, re-verified this morning.

So: two climbing, two growing, one slowed, three stalled.

The pick we got most wrong

Ghost in the Droid was the lead entry last week. It had the demo video, the nine reels, the active account, plus 99.1% on AndroidWorld driven by Claude Code. It was the only pick with real media behind it.

Eleven stars in eight days, however.

The media presence that made it look strongest turned out to be the least predictive signal on the list. Somebody had built an audience deliberately, then the audience did not convert into anybody actually using it.

The one that went sideways in a good way

shuohao-skills went from 246 stars to 1,573, plus 27 forks to 181.

It also changed what it is. Last week the description read as a skills collection for coding agents with an unusual creative lean. This week the repo describes itself explicitly as skills for AI short-drama production: breaking down characters, arranging outlines, scene and prop settings, script writing, storyboarding.

So it was never really a coding tool. It was a video production pipeline that happened to run on coding agents. The 539% growth came from an audience nobody covering agent tooling was watching.

smux is the honest failure

Last week it went in the “moving but not new” section at 1,499 stars on 161 days.

Meanwhile it gained 11 stars in a week and has had no commits for 19 days. The verification script now flags it as stale, which it did not last Saturday.

Calling something “moving” was wrong. It was coasting on old momentum, plus a week of data made that visible in a way one snapshot could not.

Why This Week Looks Like This

A roundup where seven of eight picks share one dependency deserves an explanation rather than a shrug.

Two things happened at once. DeepSeek Harness launched with genuine gaps: no terminal interface, no desktop app, no plugin discovery, no Windows bash. Meanwhile it shipped as a plugin kernel where every capability swaps out, plus a published topic tag for finding plugins.

So the gaps were obvious and the extension path was documented. That combination is unusual. Most launches have one or the other.

The result is that four days produced tooling which normally takes a year. Not because anything was hard, but because a few hundred developers all spotted the same missing pieces on the same morning.

Whether it holds

Whether that holds is the open question. Ecosystems built this fast usually shed most of their entries within a month, since the early plugins solve problems the platform eventually solves itself. A first-party desktop client would make four community ones redundant overnight.

Which is exactly what next week’s revisit will measure. Eight picks, all depending on a runtime whose README promises compatibility-breaking changes in capitals.

The prediction, on the record: expect more stalls next week than this week. Anything solving a gap DeepSeek fills themselves has a short life, plus the plugin interfaces are explicitly unstable.

Being wrong about that in public is the point of running the revisit at all.

What Got Cut

Three repos scored well on velocity and did not make it.

SheberDavid/v4-flash-godmode-opencode-go gained 484 stars a day, the highest velocity anywhere in this scan. No license file. Unlicensed means all rights reserved by default, whatever the README claims, so installing it gives you no legal right to use it.

hairyf/deepseek-harness-desktop reached 280 stars, a 5MB Tauri build in Rust that looks like the cleanest desktop client of the four. GitHub returns NOASSERTION on its license, meaning something is there that cannot be automatically identified. Watch it, plus send a pull request asking for clarity.

Nervercc/gpt_nerver gained 157 a day under MIT and describes itself as a ChatGPT Plus automation toolkit with a registration engine plus card and PayPal handling. That is account creation tooling. Technically open source, cut on grounds nothing to do with licensing.

Roughly a third of every scan fails on the license column alone. This week most of the fastest-growing DSH plugins had no license at all, which is what happens when an ecosystem forms in 72 hours and nobody stops to add a file.

What the Ecosystem Tells You

Step back from the individual repos for a moment.

In four days DeepSeek got a marketplace, four desktop clients, a mode router, a Windows compatibility shim, an anime plugin, plus a documentation project reverse-engineering its system prompts. All from strangers. All free.

That is what a platform strategy actually looks like when it works. DSH shipped as a plugin kernel where everything swaps out, then published a topic tag, then stood back.

Two things cut against the enthusiasm, though.

Almost all of it is written in Chinese with no English documentation. If you only read English roundups you are seeing a fraction of what shipped. Six of this week’s eight picks have Chinese-language READMEs.

And the licensing is a mess. The fastest-moving projects skipped it entirely, which means the most popular plugins for a permissively licensed runtime are themselves not usable in anything serious.

Ecosystems that form in 72 hours form sloppily. Whether this one hardens or evaporates is exactly what next week’s revisit will show.

How to Judge One of These Yourself

Six days until the next issue, so here is the check meanwhile.

Read the license file, not the README

No license means all rights reserved. MIT and Apache 2.0 are the safe defaults. NOASSERTION on GitHub means something is present that could not be identified automatically, which is worth asking about before you build on it.

Check the creation date against the star count

A repo with thousands of commits pushed last Tuesday is a private codebase that just went public, which is a different risk profile from a project built in the open. The creation date sits on the API.

Look at forks against stars

Stars are bookmarks. Forks mean somebody cloned it to use or change. opendot has 37 forks against 35 stars, which is unusual and suggests the people who found it needed it.

Check open issues against stars

Twenty-seven issues on 258 stars, as with the router above, means heavy use. Zero issues on a thousand stars usually means nobody is really running it.

Check the last push date

The one I missed on smux. A repo can look healthy on stars while nobody has touched the code in three weeks. Stars are historical, commits are current.

Five minutes per repo filters out most of what would waste your afternoon.

Before You Install Any of This

Obviously everything here is days old, plugging into a runtime that carries a capitalised warning about compatibility-breaking changes.

Agent frameworks execute code with your permissions. We covered an operator whose agent published his API keys to the open internet because it started a web server in the wrong folder, plus an assistant that cancelled a stranger’s gym booking because nobody told it not to.

Use a container or a throwaway machine. Scope your API keys. Never run an unfamiliar agent from a directory holding anything you would mind seeing published.

The desktop clients deserve extra caution especially. A bundled Node runtime from an account with no history, installed with a double-click, is a lot of trust to extend to a two-day-old project.

The Part Worth Keeping

Three of last week’s eight picks stalled inside seven days, including the one that led the issue.

That is roughly the hit rate to expect, generally, when you rank by growth rate instead of waiting for consensus. Catching things early means catching things before anyone knows whether they work.

The alternative is writing about them in three months alongside everybody else, when the interesting part is over.

Next Saturday this week’s eight get the same treatment. Given that seven of them depend on a runtime that is four days old, expect that table to be uglier than this one.

One more thing the revisit taught us. Stars are a lagging measure of attention, forks are a leading measure of use, plus the last push date is the only one that tells you whether anybody is still working. smux looked healthy on every metric except the one that mattered.

That check is now part of the process. It costs ten seconds per repo and it would have kept a coasting project out of issue 01.

Charts and Blocks

Last week revisited

This week’s eight, verified

FAQ