"Spotify cut Claude Code's bill by 90%": a plugin most people can't install, how it got 3,000+ stars
What it is A plugin repo Spotify built for its commercial Backstage (Portal) AI features. The stars mostly come from shunt: a hook that blocks Claude Code from reading a big file whole, hands it to a cheaper model, and returns a short summary.
Why it blew up The Spotify name, plus a headline that's easy to retell ("Claude Code cuts 90%"), hits developers right where their token bills hurt. It hit HN and the trending charts in September; 11-01 a big LinkedIn account then described "one PM's test" as "Spotify's bill" and pushed it back onto the trending charts.
CHow you could follow it Don't build another token-saving plugin or a Portal-free port (a dozen of those stalled at 0–7 stars). Build the part it got wrong: a measurement tool that reads your local logs and shows where tokens actually go, plus a write-up with real numbers for HN and Reddit.
- Data (updated daily) · Repo created 2026-07-23 · 3,181 stars · 7 days +658
GitHub · stars Data 2026-10-09 → 2026-11-08 (31 days, 25 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
spotify/portal-ai-plugins is the plugin repo Spotify built for its commercial Backstage (Spotify Portal). Almost all the stars are for one plugin inside it called shunt: it stops Claude Code from reading large files and hands that work to a cheaper model, claiming a 90% token saving. The stars came in two waves. The first was in September, from an engineering blog post and HN. The second was in early November, when the repo had gone two months without a commit. A LinkedIn influencer reframed it, and it gained 600+ stars in a week, reaching 11-06 at 3,167. But using shunt requires a paid Portal, and most people who starred it can't install it. Below: what it is, where the stars came from, why the copycats got none, and what you can take from it.
One PM's "my" became Spotify's "their bill"
In 2026 September 3, Spotify's engineering blog published "Portal by Spotify cut my Claude Code token usage by 90%". The author, Dimitri Mazmanov, is a Portal product manager. He opens with: "Most of what AI coding agents do for me isn't thinking, it's I/O." Reading five files to answer a question about one method, or writing a new file by copying the pattern of twenty test files beside it, all burns tokens on the most expensive model. He cited a Gartner prediction that by 2028, AI coding spend would exceed the average developer's salary.
His fix was two "modes" in Portal, bulk-reader and code-writer, both using Gemini 2.5 Flash in the post. When Claude Code tries to read a file longer than 350 lines in full, a hook intercepts the read, has the cheaper model process it, and returns only a short summary to Claude. The test ran on a 162k-line Java monorepo. Three file reads saved 82%, 94%, and 94%, and the average across them is the 90% in the headline.
The next day it hit HN with 278 points and 178 comments, mostly skeptical. One said, "Gemini 2.5 Flash writing code? I wouldn't dare", and several argued the post itself read as AI-written: "this is full of Claude-speak."
Two months later, on Nov 1, LinkedIn influencer Aakash Gupta posted: "Spotify cut their Claude Code token bill by 90%. Then they open-sourced how they did it." He attached a screenshot of the shunt README and got 3,756 reactions and 135 comments. "My token usage" became "their bill": one person's test was retold as a company's bill.
What it is
The repo was created in 7-23, made public in 8-11, is Apache-2.0 licensed, has no repo description, and has 3 contributors. It contains two plugins:
- portal: a set of skills that call the Portal CLI to search services, run actions, and file feedback. In October it added a skill for cross-repo bulk code changes (Fleetshift). Only Portal customers can use it.
- shunt: Claude Code only, in three layers. Layer one is a hook that blocks Read calls over 350 lines and cat/head/tail. Layer two is two scripts that pass the work to a cheaper model configured in Portal through the Portal CLI. Layer three is a skill that tells Claude when and how to call those scripts. A frequently quoted line from the blog: a rule in CLAUDE.md is "just a suggestion, Claude can ignore it", so you need a hook to enforce it.
shunt requires a Spotify Portal instance with AiKA enabled. For most individual developers, that one condition shuts the door.
How the stars came
| Timeline | Daily gains | What happened |
|---|---|---|
| 9-03 / 9-04 | No data | Published on the engineering blog; hit HN the next day, 278 points |
| 9-05 ~ 9-12 | 9-11 +102,9-12 +263 | Techzine, dev.to, Medium, YouTube, and Reddit r/ClaudeAI followed up; 9-12 reached #7 on the TypeScript trending chart |
| 9-17 ~ 9-22 | +82 ~ +145 | Secondhand tutorials and reviews followed |
| 10-12 ~ 11-01 | 0 ~ 18 per day | Mostly stalled, with no commits after 10-23 |
| 11-01 ~ 11-02 | 11-02 single-day +210 | Aakash Gupta's LinkedIn post, reshared by a wave of people |
| 11-03 ~ 11-05 | +115, +149, +151 | Reached the GitHub-wide trending chart (best rank #7); aggregator sites, podcasts, and Instagram repost accounts passed it along |
| 11-06 | +19 | Decline |
(September data comes from Trendshift daily star counts; from October on it's GitHub daily snapshots. The two sources split days about a day apart.)
It gained 646 stars in the last 7 days, with only 8 in the first 7 days. The fork timing matches the two waves: 79 forks between 9-09 and 9-12, and 43 between 11-01 and 11-04. I spot-checked twenty-odd forking accounts, mostly long-standing real accounts, with no sign of star-farming.
The second wave can be traced to LinkedIn. A developer named Jason MacLulich 11-02 wrote a blog post whose first line says the article was "spread on LinkedIn as Spotify cut Claude Code's bill by 90%." I didn't find evidence of anyone pushing it on X.
The 90% is real, but most people's bills can't use it
MacLulich's post is worth a closer look. He replayed four weeks of his own Claude Code logs (170k model calls, roughly $10k at API list prices) and calculated how much shunt would actually intercept. Full-file reads over 350 lines accounted for only 0.8% of spend, and even at a 90% discount that saves under 1%. 62% of his Read calls already had line ranges, so the hook would let them through. The money goes to the context the agent carries on every call: cache reads alone are 53% of it.
He also fairly defends Spotify on one point: the original title says "my", the author admits the cheaper model "missed a subtle thread-safety bug", and debugging and architecture work should stay with Claude. The overstatement came from the LinkedIn round.
So most of those 3,000+ stars amount to "bookmarking the idea." The number of people who actually installed shunt isn't visible from outside, and is probably small (inference).
Why the copycats got none of the stars
Within three days, shunt's idea had been ported into versions that don't need Portal: SalehB1/shunt-anywhere ("no Portal tenant needed"), lucass3na/relay-plugin, alexanderradahl/shunt-muse (also supports Codex), and p5/read-shunt-plugin (for OpenCode and Codex). In November's second wave, federicoimparatta/shunt-claude and others appeared. A Reddit post also said, "I forked Spotify's shunt and it runs without Portal." Each of these repos sits between 0 and 7 stars.
The reason is simple: people starred for the headline "Spotify + Claude Code + 90%", not for the code. The ports are actually more usable as products, but they don't have that headline, or an engineering blog, an HN front page, or a big LinkedIn account behind them.
Look at the neighbors, too. "Make Claude Code burn fewer tokens" is already a crowded lane:
| Project | Stars | Compared with shunt |
|---|---|---|
| JuliusBrussee/caveman | 118k | Compresses model output and wording, no service needed |
| rtk-ai/rtk | 86k | Rust single-file CLI that compresses output of common commands |
| oraios/serena | 31k | MCP, searches and edits by symbol instead of reading whole files |
| zilliztech/claude-context | 13k | Vector search over the codebase, returns only relevant snippets |
| Mibayy/token-savior | 1,209 | MCP, trims file reads |
| pleaseai/shunt | 261 | Same name, routes agents to other models at the inference layer |
| Built-in Claude Code subagents / Explore | Everyone has it | Official "cheap model scouts ahead", works with cheap models |
(GitHub, 11-06.)
In this table, portal-ai-plugins is mid-sized, and the only one that depends on a paid platform. Its one distinctive trick, a hook that enforces the block and hands the whole file to another model, was copied within three days.
It's really an ad
For Spotify, the repo is acquisition content for Portal and AiKA. The blog shows you how to set up two modes in Portal, the repo asks you to star and share, and the money comes back as Portal enterprise subscriptions. The playbook itself is worth learning:
- One person, one concrete number: "cut my … by 90%" travels about ten times better than "a token routing scheme".
- Hit the sorest spot: in 2026, developers' biggest anxiety is the token bill, and repos like this routinely get high stars.
- An idea that's easy to explain: "suggestions aren't enough, you have to enforce them" carried a pile of secondhand tutorials and videos.
- When the heat fades, repackage it: the product didn't change a line, "my" became "their bill", and a repo that had sat untouched for two months trended again.
If it were you
C: there's something to learn, but copying it isn't worth it. Its stars came from Spotify's name and one easily repeated headline, neither of which you can get. Open-source projects doing the same thing already have tens of thousands of stars, and a dozen ports all stayed in single digits.
Who it suits: developers already building AI coding tools who want to learn how "one person + one number" headlines work, and people with real usage data who can write a credible review.
Who it doesn't suit: anyone planning another "token-saving plugin" or a "shunt that works without XX". That path has been tried, and the result was 0 to 7 stars. Also anyone with no distribution channel who expects good code to be found on its own.
How to do it: if you follow this trend, build the part it got wrong, not the part it got right. shunt's biggest gap is the one MacLulich pointed out: nobody knows where their tokens actually go. Build a "measure first, then cut" tool that reads local Claude Code / Codex logs, shows whether the spend goes to cache, tool output, or file reads, and then recommends something like caveman, rtk, or shunt. The result of a tool like this is a number people can repost ("I measured four weeks, this 90% only saves me 0.8%"), so the headline comes built in.
How to get users: Copy Spotify, and copy MacLulich too. Run the tool on your own real bill (or a few friends'), then write a post with concrete numbers, titled in the format "X says it cuts my bill by 90%, I measured it." Post to HN, Reddit r/ClaudeAI and r/ClaudeCode, then find accounts on LinkedIn / X that make AI coding content and get them to repost. Put a chart of "where your money goes" on the first screen of the README.
Window: "Cutting tokens" is a hot topic tied to Claude Code pricing and usage. As long as the token bill is developers' biggest worry, the topic stays alive. But measurement tools are easy for vendors to build into the product (Claude Code already ships a usage breakdown), so I'd estimate the window closes before the first half of year 2027.
Signs we're wrong: ① Your review post hits the HN front page, but the repo still isn't at 100 stars a week later. That means the "cut tokens" topic is already played out. ② Claude Code or Codex ships an official usage report split by category, and a measurement tool has no reason to exist. ③ The other way around: if a port with no big-company backing gets thousands of stars, the product itself can carry star count, and it's worth going back to "build a better shunt."
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one JuliusBrussee/caveman Open source 2026-04 117,929 star Compresses model output and wording, runs without other services, an order of magnitude bigger in scale rtk-ai/rtk Open source 2026-01 85,717 star Rust CLI proxy that compresses output from common dev commands, zero dependencies oraios/serena Open source 2025-03 31,146 star Semantic search and editing by symbol, no reading whole files, no model swap zilliztech/claude-context Open source 2025-06 12,673 star Searches the codebase with vector retrieval, so only relevant snippets go into context Mibayy/token-savior Open source 2026-03 1,209 star MCP, slimmed-down file reads and context pleaseai/shunt Open source 2026-07 261 star Same name, but routes to other models per agent at the inference layer Built-in Claude Code subagents / Explore Big-company features 2025 All Claude Code users Official native "cheap model for exploration," with no hook forcing blocks and no third-party backend - Where users come from
- Verified Own engineering blog (content marketing): 2026-09-03 engineering.atspotify.com "Portal by Spotify cut my Claude Code token usage by 90%," written by Portal's PM
- Verified Hacker News: 2026-09-04 on HN, 278 points / 178 comments (our HN database, item 49571465)
- Verified Tech media and secondhand tutorials: Techzine 9-07, dev.to/Medium 9-05, thakicloud 9-08, explainx 9-10, wavect 9-12, several YouTube videos
- Verified GitHub trending: Trendshift: 9-12 TypeScript #7, 11-01 #13; data card best site-wide rank #7
- Verified Large LinkedIn accounts: 11-01 Aakash Gupta posted "Spotify cut their Claude Code token bill by 90%" with 3,756 reactions and 135 comments. MacLulich's blog also says the claim spread on LinkedIn 11-02
- Verified Reddit: r/ClaudeAI "Cut your Claude Code cost by 90% using the Spotify Method," r/BestGitHubRepos
- Verified Auto-aggregator sites and Instagram repost accounts: 11-03 to 11-05: readmex, AIToolly, earlysignal, getai.app, Zeno.FM's GitHub Daily Trend, IG @ai.git and Git Scope
- Inferred X: Not found in our X corpus
spotify/portal-ai-plugins: why it got 3000+ stars
Research date 2026-11-06. Data from our github database (repo_day), the GitHub API, Trendshift, our HN database, and web pages found via Jina/Exa.
Bottom line
This is the official plugin marketplace that connects Spotify's commercial Backstage (Spotify Portal) to Claude Code / Codex / Cursor / pi. Most of the stars are for the shunt plugin inside it. It uses hooks to intercept large file reads and hands the file-reading and boilerplate-writing work to a cheaper model (the post uses Gemini 2.5 Flash), claiming "Claude Code token usage cut by 90%." Both waves of stars were driven by the title of the same Spotify engineering blog post: the September wave by the blog plus HN, and the November wave by LinkedIn influencers repackaging it as "Spotify cut its Claude Code bill by 90%." Spotify's brand, the "cut tokens" pain point, and a number that's easy to repeat add up to these stars. The product itself is barely usable: shunt needs a paid Portal instance and AiKA to run, so most people who starred it can't actually install it.
What it is
- Repo created 2026-07-23, made public 8-11 (commit "prepare public plugin release"), Apache-2.0, no repo description. 3 contributors (Djam, Dimitri Mazmanov, Jonatan Dahl), last commit 2026-10-23 (GitHub API).
- Two plugins included:
- portal: a set of skills that call
npx @spotify/portal-cli: setup/doctor/search/service/actions/feedback. 10-21 added Fleetshift-related skills (batch code changes across repos). - shunt (Claude Code only, 8-14 added): a PreToolUse hook blocks Read calls over 350 lines and cat/head/tail, and has Claude call bulk-read / code-write scripts instead. The scripts pass the work through Portal CLI's
aika:invoke-chatto the AiKA mode configured in Portal (the cheaper model). The README claims "82–94% token savings on large file reads and boilerplate generation."
- portal: a set of skills that call
- Prerequisites: a Spotify Portal instance (the commercial SaaS version of Backstage) with AiKA enabled.
Growth data
- Our github database: 10-09 at 2447 stars; from 10-12 to 11-01 it gained only 0–18 per day. Single-day gains: 11-02 +210,11-03 +115,11-04 +149,11-05 +151,11-06 +19, reaching 3167. Last 7 days: +646; the 7 days before that: +8.
- Trendshift (daily star/fork counts and TypeScript trending rank): 9-11 +102, 9-12 +263 (TypeScript trending #7), 9-17 +82,9-18 +145,9-22 +135; October mostly stalled; 11-01 +250 (TypeScript #13), then 11-03 +160,11-04 +122,11-05 and falling back. (Trendshift and our database differ by about a day in daily bucketing. Its star count for 9-7 to 9-10 is 0, but it shows 6–26 forks. We suspect data is missing for those days.)
- Fork timing (GitHub API, 250 forks total): 9-09 to 9-12 had 79, 11-01 to 11-04 had 43. Both waves line up with the star timing. Spot-checking 24 forking accounts, most are older real accounts with their own repos. We saw no sign of bought or bot activity.
- On the data card, the best GitHub site-wide trending rank was #7, and it held that for 2 days.
Where users came from (growth tactics)
Wave one (September): Spotify engineering blog, then HN
- 2026-09-03 Spotify's engineering blog published "Portal by Spotify cut my Claude Code token usage by 90%," written by Portal PM Dimitri Mazmanov (engineering.atspotify.com/2026/9/…, with a copy on portal.spotify.com/blog). It's essentially product marketing: it walks you through setting up two AiKA modes, then installing shunt.
- 2026-09-04 hit HN: 278 points, 178 comments (our HN database, item 49571465). Many comments were skeptical ("Gemini 2.5 Flash for coding?", "AI slop article").
- Media and secondary content followed: Techzine (9-07), aipricing.guru (9-05), dev.to/Medium's "Spotify Cut Claude Code Token Usage by 90 Percent. The Pattern Works in Any AI Agent" (9-05), thakicloud's retest (9-08), ClaudeMap listing (9-08), explainx (9-10), wavect review (9-12), ai-tldr, YouTube videos ("Spotify's Shunt Saves 90% of Claude Code's Tokens," "EXPOSED: Spotify Cut Its Claude AI Bill by 90 Percent…"), Reddit r/ClaudeAI "Cut your Claude Code cost by 90% using the Spotify Method," and a batch of LinkedIn reshares.
- 9-12 entered the GitHub trending chart (Trendshift TypeScript #7), and the trending placement brought another round.
Wave two (November 1–5): LinkedIn influencers repackaged it, then GitHub trending, then aggregator sites reposted it
- On 2026-11-01 04:16 UTC, LinkedIn influencer Aakash Gupta posted "Spotify cut their Claude Code token bill by 90%. Then they open-sourced how they did it." with a screenshot of the shunt README, getting 3,756 reactions and 135 comments. He turned one PM's personal test into "Spotify's bill."
- Same-day follow-ups: on LinkedIn, Ferdous Mahmud Shaon(11-01) and Rubén Domínguez Ibar(11-02) and others reshared it; in Spanish, noticias.ai and revistacloud(11-01). There's also pushback, like Jason MacLulich's blog 11-02, "Spotify's 90% Claude Code saving would be under 1% on my bill", which opens with "it's been going round LinkedIn as Spotify cutting its Claude Code bill by 90%". That's an independent source confirming the wave was driven by LinkedIn.
- Then it hit the GitHub trending chart (best site-wide rank #7), and auto-aggregator and Instagram repost accounts followed: earlysignal, aikaschool, wrabby (11-03); readmex, AIToolly, getai.app, DigiNews, and Zeno.FM's "GitHub Daily Trend" podcast (11-04); Instagram @ai.git (11-03, "hidden gem… comment REPO and I'll DM you the link") and Git Scope (11-04); Reddit r/BestGitHubRepos (titled 2.9k stars).
- During the second wave the repo had no new commits (the last one was 10-23), so it wasn't a product update driving it.
X: Neither our X corpus (about 560 people in the five core circles) nor live search turned up any relevant posts. Whether someone pushed it on X can't be confirmed.
Competitors (all of them are "make Claude Code use fewer tokens / read fewer files")
| Name | Form | Launched | Scale | How it differs from portal-ai-plugins |
|---|---|---|---|---|
| JuliusBrussee/caveman | Open source skill + proxy | 2026-04 | 117,929 star | Compresses model output and phrasing; runs without any other service; an order of magnitude bigger in scale |
| rtk-ai/rtk | Open-source Rust CLI proxy | 2026-01 | 85,717 star | Compresses the output of common dev commands, claiming a 60–90% saving; single binary, zero dependencies |
| oraios/serena | Open source MCP servers | 2025-03 | 31,146 star | Symbol-level semantic search and editing without reading whole files; doesn't swap the model |
| zilliztech/claude-context | Open source MCP servers | 2025-06 | 12,673 star | Uses vector search over the codebase and only puts relevant snippets into context |
| Mibayy/token-savior | Open source MCP servers | 2026-03 | 1,209 star | Trims file reads and context |
| pleaseai/shunt | Open-source proxy | 2026-07 | 261 star | Same name; routes requests to other models per agent at the inference layer |
| Plugins like Frugal that get posted on Reddit for routing | Open-source plugins | 2026 | Small | Routes work to the cheapest model that can handle it |
| Claude Code's built-in subagents / Explore (can be configured with a cheap model) | Big-company features | From ¥2025 | All Claude Code users | Official native "cheap model explores"; no hooks forcing it, no third-party backend |
Verdict: several open-source projects doing the same thing already have tens of thousands of stars. portal-ai-plugins is mid-sized among them, and it's the only one that can't run without a paid platform.
Copycats
All are ports that "remove the Portal dependency," each with 0–7 stars: SalehB1/shunt-anywhere (9-09, "no Portal tenant needed"), lucass3na/relay-plugin (9-08, delegates via claude -p), melonkernel/shuntkit (9-14), alexanderradahl/shunt-muse (9-21, supports Claude Code + Codex), trinaldirizki/hermes-shunt (9-12), p5/read-shunt-plugin (9-07, OpenCode/Codex), eigozatsudan/token-shunt-plugin, federicoimparatta/shunt-claude (11-01, Claude-only version), AdityaInamdar334/spotify_shunt_routing_lab (11-02). On Reddit, r/ClaudeCode and r/claudeskills both have posts like "I forked Spotify's shunt plugin so it works without Spotify Portal."
Why it's working
- A big-brand name plus a quotable number: the title "Spotify + Claude Code + 90%" can be repeated in one sentence by anyone. The Spotify org has 110k stars in total, and the engineering blog itself has distribution power.
- Hits the most painful spot: In 2026, Claude Code token costs are one of the things developers worry about most (the blog opens by citing Gartner: "by 2028, AI coding costs will exceed the average developer's salary"). "Save tokens" repos generally get very high star counts (caveman and rtk both reached 80k).
- Easy to copy and easy to explain: a three-layer setup of hook enforcement + script + skill. The point that "advice isn't enough, you have to force it" keeps getting retold as a tutorial in secondhand articles, giving content creators material to write about.
- The second wave was just the same thing spread again with new wording: the product hadn't changed. A LinkedIn big account recast "one PM's test" as "Spotify's bill," and one post with 3,756 replies pushed a repo that hadn't moved in two months back onto trending. Aggregator sites and repost accounts amplified it afterward.
- Stars only mean "bookmarking the idea": shunt requires Portal and AiKA, which most people can't install. So people who actually use it mostly go for the dependency-free copycats or write their own. Star counts far exceed actual usage.
Differentiation
- Compared with its peers, what's really different is: it uses hooks to force interception, plus hands the whole job of reading files to another model (large files never enter Claude's context), instead of compressing or retrieving context. But the approach was ported into a version without the Portal dependency within three days, so the moat is zero.
- Its real "differentiation" is the Spotify name and the Portal ecosystem, and that is also its weak point (it requires a paid platform). So the reason it took off is the brand and the story, not differentiation. For Spotify, this repo is lead-generation content for Portal / AiKA: the money comes back through Portal's enterprise subscriptions, not from the open-source plugin.
How many people have seen it
It has already been widely discussed: 278 points / 178 comments on HN, covered by tech media like Techzine, one LinkedIn influencer post with 3,756 replies, plus multiple YouTube videos, Reddit threads, and a dozen or so copycat ports. This space is already crowded.
What others can borrow
- Use an open-source repo as lead-generation content for an enterprise SaaS: write an engineering blog post around "one person + one specific number" ("cut my … by 90%"), then release the repo and let people star it.
- Once the first wave of heat fades, swap in a sharper framing via LinkedIn / X big accounts (individual → company, "my" → "their bill") and push it again; old repos can also get a second run on trending.
- For indie developers, the real opportunity is "turning what big companies only offer tied to their own platform into a version that depends on no platform." But none of these ports got stars, which shows that porting alone isn't enough; you still need your own distribution.
Still unclear
- Whether any big X accounts pushed it around 11-01 (our corpus has nothing on this).
- The explainx article is dated 9-10 but says "about 2,900 stars," which doesn't match our October data (about 2,450–2,500). It was probably edited later; not verified.
- Trendshift star data for 9-07 to 9-10 is missing, and how many stars the HN day actually brought in is unclear (GitHub's stargazers endpoint now returns 404, so per-star timestamps can't be pulled).
- There is no public data on actual shunt / Portal install counts or how many enterprise leads Portal got from it.
Sources
- github.com/spotify/portal-ai-plugins (README, plugins/shunt/README.md, commits, forks API)
- engineering.atspotify.com/2026/9/portal-by-spotify-cut-my-cl…
- news.ycombinator.com/item?id=49571465 (our HN library: 2026-09-04,278 points / 178 comments)
- trendshift.io/repositories/230238
- www.linkedin.com/posts/aagupta_spotify-cut-their-claude-code… (2026-11-01,3,756 replies)
- maclulich.com/blog/spotify-90-percent-claude-code/(2026-11-02)
- www.techzine.eu/news/devops/144093/spotify-reduces-claude-co…
- www.reddit.com/r/ClaudeAI/comments/1wbmcgw/, www.reddit.com/r/ClaudeCode/comments/1wmq959/, www.reddit.com/r/BestGitHubRepos/comments/1xnxaix/
- www.instagram.com/reel/DfTJlrQjYxm/ (@ai.git, 11-03), www.instagram.com/p/DfUUSR-k_qD/ (Git Scope, 11-04)
- Aggregator sites: GitHub Daily Trend on earlysignal.news, readmex.ai, aitoolly.com, getai.app, zeno.fm (11-03 to 11-05)
- Our github library repo_day (2026-10-09 to 11-06)