# One sentence to paste into an agent to set up 69 quality gates in your repo: where dev-quality-gates' 300 stars came from · GitHub open source projects

> Source: https://stringers.io/en/github/gh_mokevnin__dev-quality-gates.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> It rode the hot topic of "how to keep agent-written code in check" and is usable the same day it's read; but the stars mainly came from the author's TG channel with roughly 16k subscribers and a podcast with roughly 40k views per episode, and it doubles as the traffic sample for his AI coding course.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

mokevnin/dev-quality-gates · mokevnin

# One sentence to paste into an agent to set up 69 quality gates in your repo: where dev-quality-gates' 300 stars came from

**What it is** A GitHub repo that lists 69 code quality tools by language and scenario, recommends one tool per job, and gives you a paragraph for Claude Code / Codex to wire the right checks into your project and CI.

**Why it took off** It landed on the trending topic of "how to keep agent-written code under control," and it's usable the same day you read it. But the stars mainly came from the author's Telegram channel (about 16k subscribers) and a podcast episode (about 40k views), and the repo doubles as a free sample for his AI coding course.

**C** **How you could follow** Don't just build another generic version. Pick a domain it doesn't cover (mobile, data engineering, infrastructure, design systems) or do the same "one-sentence agent setup" checklist in a different language, publish it first in channels where you already have an audience, and two weeks later ship a long-form piece for a second wave.

Grade C: the format (curated checklist + an agent-facing setup prompt) is fresh and easy to copy, and the vertical niches are still empty. But its traction came from the author's own Russian-speaking audience and course ecosystem, which followers don't get, and the repo itself has only 300 stars. Anyone copying it without an audience will have a low ceiling. It's spreading in small circles

Data (updated daily) · Repo created 2026-10-23 · 324 stars · 7 days +159

GitHub · stars

Data 2026-10-25 → 2026-11-08 (15 days, 15 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

On the afternoon of Oct 24, 2026, Kirill Mokevnin, co-founder of the Russian programming school Hexlet, posted in his Telegram channel under the title "Quality Gates всем и пусть никто не уйдет обиженным" ("Quality gates for everyone, and nobody leaves empty-handed"). He said he'd spent years trying out checking tools on Hexlet projects, had gathered enough, and turned them into one repo. Usage is a single step: open your coding agent, paste the link, and have it suggest improvements against your project. The post got about 7,000 views. Two days later the repo gained 55 stars in one day, and two weeks later it was at 299. Below: what it is, where the stars came from, how it differs from a pile of linter lists, and which parts of this you can copy and which you can't.

### What it is: a conclusions-only checklist plus a paragraph for agents

dev-quality-gates is a tool list. The CC0 protocol, and the first line of the README says "This is not an awesome list." 11-06 counted the README: 31 categories, 69 tools. Half the categories are split by language (JS/TS, Python, Go, Rust, Ruby, PHP, Java, Kotlin, .NET, Swift, Elixir, Shell), and half cut across them (GitHub Actions, GitLab CI, database migrations, API contracts, secret leaks, Docker and Terraform, Git commit conventions, agent config files...).

What separates it from an ordinary list is in the principles at the top:

- **One tool per job** , rarely two. Python gets Ruff, ty, deptry, import-linter, each covering one thing.

- **It must be able to fail the build.** "A report nobody reads doesn't count": tools have to return a non-zero exit code on violations.

- **Agent-friendly** : non-interactive, machine-readable output, safe automatic fixes. The README's words: "AI coding agents are first-class users of these tools."

- **No filler.** One section lists categories it hasn't settled on yet, like container image scanning: Trivy's GitHub Action was compromised in March this year, so the author would rather leave the slot empty than fill it carelessly. Tools that were evaluated and rejected are recorded separately in a not-adopted document.

The list is generated from a single tools.json, and each tool records a review date and a source. A weekly automated job flags archived or long-unmaintained tools for re-review.

The most important part is the "Use it in your project" section of the README, a paragraph you can paste verbatim into Claude Code or Codex:

```text Apply https://github.com/mokevnin/dev-quality-gates to this repository. Read and follow https://raw.githubusercontent.com/mokevnin/dev-quality-gates/main/docs/adopt.md. Show me the plan before you change anything.```

The agent reads an instruction written for it, checks what your project uses, picks only the relevant entries, shows you a plan first, then wires the checks into git hooks and CI, and "proves every check can fail." This paragraph was added on day three of the repo (10-25); the earlier TG post gave a single Russian prompt instead.

### How the stars came in: two waves, both triggered by the author himself

The repo was created late at night on Oct 23; in 14 days it gained 299 stars and 15 forks (GitHub, 11-06). The curve is clean, with each of the two jumps lining up with one of the author's own launches:

| Date | star | What happened |
|---|---|---|
| 10-22 | Before the repo | The author announced on TG that he was personally leading the first session of Hexlet's "ИИ для разработчиков" (AI for developers) course, whose first lecture outline included "hooks, linters, ast-grep and other guardrails." |
| 10-24 | — | The TG channel @orgprog (about 16k subscribers) posted about the repo, with about 7,000 views and about 157 reactions. |
| 10-25 | 42 | Added the "paste one sentence to your agent" setup instructions; Russian-speaking developers started opening PRs. |
| 10-26 | 97 (+55, the single-day peak) | The post kept spreading. Hexlet's volunteer project hexlet-sicp opened issues the same day to refactor against the checklist, and a Nigerian developer listed it on LinkedIn as one of "this week's 3 open source AI repos." I didn't find out who drove the traffic on that day. |
| 10-27 to 11-01 | 120 → 165 | Natural decline, from +3 to +17 per day. |
| 11-01 | — | The author's podcast "Организованное программирование" released a solo episode on how to control code written by agents; about 40k views on YouTube (4 days after publication). It was also posted to TG (about 6,100 views), X (about 2,200 views) and LinkedIn. |
| 11-02 to 11-05 | 182 → 293(+111) | Second wave |
| 11-06 | 299 |  |

The English-speaking world barely reacted: nobody posted it on Hacker News, searches for the repo name or author on X turned up no discussion, and the only find was a small LinkedIn roundup. That the stars mainly came from Russian-speaking developers is an inference, based on the channels, the people opening PRs, and the adopters all being Russian-speaking (the stargazer list wasn't sampled).

One more detail: the repo's footer and every TG post carry links to the Hexlet AI course. The list is, in effect, a public sample of that course. The author 10-22 wrote in a post that developers today "no longer need to hear what MCP is or how to write agents.md; they want an automated workflow that produces reliable code," and this repo is that claim made concrete.

### Why it took off

**The author is the distribution channel.** A 16k-subscriber Telegram channel, a podcast pulling tens of thousands of views per episode, a 1,343-follower GitHub account, and a whole community of Hexlet learners and volunteers. Both star waves line up with his own posts. Neither came from a third-party megaphone.

**Timing was right.** In the second half of 2026, "how to keep code written by agents under control" became a hot topic in the developer community. Similar repos kept popping up on GitHub from 6 through September, and several have already passed 1,000 stars.

**Usable the same day.** A typical linter list leaves you to pick and configure everything yourself. This one hands the picking and configuring to an agent, so a reader pastes one paragraph and sees results within a minute. There's proof it gets used: hexlet-sicp opened a refactor issue, and a learner's repo opened an "Adopt Dev Quality Gates" issue. Those issues link back to the repo, which gives it a second round of exposure.

**Looks credible.** Every tool has a review date and research notes, exclusions come with reasons, and an automatic freshness check runs. In the first week, about 6 external contributors opened PRs, so the repo looks active.

To be clear, these differences help it **hold people and get used** . But the reason it **took off** is mostly the author's audience. A star count of 300, almost all from Russian-speaking developers, shows that the format alone didn't spread it on its own.

### Who's on the same path

| Project | Scale (GitHub stars, 11-06) | How it differs |
|---|---|---|
| analysis-tools-dev/static-analysis | 14,874 | Exhaustive legacy lists with hundreds of SAST tools and linters, no verdicts |
| caramelomartins/awesome-linters | 1,108 | Community awesome lists that accept everything |
| super-linter | 10,650 | A pile of linters bundled into one GitHub Action; it runs the tools but doesn't help you choose |
| MegaLinter | 2,647 | All 50 languages at once, the opposite of "pick one" |
| qlty | 3,217 | A unified quality-check CLI with a commercial cloud |
| pre-commit / lefthook | 15,686 / 9,001 | Only covers how to run hooks, not which tools to pick |
| amElnagdy/guard-skills | 1,310 (built 2026-06) | Uses agent skills as gates; a prompt layer, not deterministic tooling |
| soumatheusgomes/vibe-coding-toolkit | 2,286 (built 2026-08) | A large collection of Claude Code plugins, prompts, and gates |
| shadcn-ui/lint | 3,315 (built 2026-09) | A single linter aimed at agents, not a selection list |

"Linter lists" and "linter aggregators" are decade-old categories, with top repos above 10,000 stars. "AI agent quality gates" is a new topic this year, and a few repos on it already have thousands of stars. dev-quality-gates sits in a small overlap of the two: an opinionated curated list plus an integration guide written for agents. I haven't yet seen new repos copying this exact format.

### If it were you

**Bottom line:** the format is worth learning from, but this project isn't worth copying as a whole. Its 300 stars came from the author's 16k Telegram subscribers and podcast. Someone without that audience making the same thing will most likely not get this number.

**Who it suits:** developers who already run a real set of checks in a specific domain and have some audience: a tech blog, a newsletter, an X account with a few thousand followers, an active community, or an internal platform team. For them, turning their experience into an "agent-executable checklist" costs a few weekends and yields a project that can stay on their résumé and homepage for years.

**Who it doesn't suit:** people with no distribution who expect GitHub traffic to carry them; people who want a "big and complete" list (that ground is taken by older lists above 10,000 stars); people who want to build agent gates as a prompt collection (guard-skills and vibe-coding-toolkit already exist).

**How to do it:**

- Switch domains, not packaging. This project covers general code quality. Mobile (pre-release checks for iOS/Android), data engineering (dbt, SQL, data contracts), frontend design systems, infrastructure as code, and game engine projects currently have no list that offers "one pick per job, can fail the build, one-sentence agent setup" (inference, based on finding no similar repos in this search).

- Switching languages is also a gap: Chinese, Japanese, and Spanish developer communities each have their own big accounts and forums. A list written in the native language with adoption instructions may spread more easily in local circles than an English version (inference).

- Copy three things: a paragraph you can paste to an agent, placed on the first screen of the README; an adopt.md written for agents that requires a plan first and proof that every check can fail; and a review date on every entry, plus a "not decided yet" section and reasons for each exclusion.

- Get it working on a few of your own real projects first. A README showing "what it caught after I plugged it in" is more persuasive than a list of tool names.

**How to get users:** follow the two waves it had. On launch day, post in your own channels with a "copy this to your agent" line. A week or two later, publish a long-form piece (video, podcast, or essay) on the trade-offs behind it. The second wave is often bigger than the first. Then reach out to communities and recommenders in the domain, not general dev circles, and have the first users open "adopt" issues in their own repos. Each issue is a backlink.

**When to move:** the topic "how to control agent-written code" is still heating up, but similar repos appear every month, so the first version should ship before year-end (inference).

**Signs you've misread it:** (1) an English-language "agent-executable gate list" backed by a big account gets past 1,000 stars quickly and covers the domain you want, which closes the gap; (2) agents like Claude Code or Codex build in the ability to auto-pick linters per project and wire up CI, making the "one-sentence setup" no longer novel; (3) the reverse: dev-quality-gates keeps gaining stars in the English-speaking world through large accounts sharing it on their own, without the author releasing anything new. That would show the format itself spreads, so people without an audience are worth trying, and the judgment should be raised.

---

Data and sources: GitHub repo page, README and issue/PR lists (11-06); daily star counts from daily scrapes (from 10-25); Telegram @orgprog posts #533, #534, #538 (view counts scraped on 11-06); YouTube podcast page (view counts before and after 11-05); LinkedIn roundup post; competitor stars from GitHub (11-06). The specific source of the 10-26 single-day peak, the geographic distribution of starring users, and course conversion are unverified.

[GitHub repo ↗](https://github.com/mokevnin/dev-quality-gates)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| analysis-tools-dev/static-analysis | Open source | 2015-12 | 14,874 stars | Exhaustive SAST / linter list, no verdicts, no guidance on wiring into CI; this project picks one per category and requires that the build can fail |
| caramelomartins/awesome-linters | Open source | 2014-02 | 1,108 stars | Community awesome list that accepts everything; this project is opinionated and has review dates |
| super-linter | Open source | 2019-10 | 10,650 stars | Bundles many linters into one Action to run; this project offers pick-recommendations plus agent setup instructions |
| MegaLinter | Open source | 2020-10 | 2,647 stars | An all-50-languages aggregator; this project takes the lean "pick one" route |
| qlty | Open source | 2015 (later renamed to its current name) | 3,217 stars | A unified quality CLI with a commercial cloud; this project is free (CC0) and only a list |
| SonarQube / Qodana quality gate | Big-company features | Years | Enterprise | Metric gates inside a paid platform; this project is a lightweight open-source tool set aimed at agents |
| amElnagdy/guard-skills | Open source | 2026-06 | 1,310 stars | Gates built from agent skills (prompt layer); this project is a deterministic toolchain |
| soumatheusgomes/vibe-coding-toolkit | Open source | 2026-08 | 2,286 stars | A large collection of Claude Code plugins, prompts, and gates; this project only selects deterministic checking tools |

Where users come from

- **Verified** **author's Telegram channel @orgprog** : post #534 on 10-24 introduced the repo, about 7K views and about 157 reactions; channel has 16,162 subscribers

- **Verified** **author's YouTube podcast "Организованное программирование"** : a solo episode on 11-01 covering Quality Gates, about 39.7k views; +128 stars over the following 4 days

- **Verified** **author's X / LinkedIn cross-posts** : X post with 2,182 views; cross-posted on LinkedIn

- **Verified** **adoption inside the Hexlet ecosystem** : hexlet-volunteers/hexlet-sicp issue #2071, and adopt issues in the mbylinkin repos

- **Verified** **community contributors** : about 6 external contributors opened PRs in the first week (savinmikhail, strelov1, solar05, redb0, and others)

- Inference **English-language reposts** : a LinkedIn roundup post, "3 open-source AI repos this week"; no HN or large X accounts

## mokevnin/dev-quality-gates: why it got traction

> Research date 2026-11-06. Channel: GitHub. Data card: created 2026-10-23, currently 299 stars / 15 forks, +153 over the last 7 days.

### Bottom line

This is a list of "AI coding agent quality gate" tools that Kirill Mokevnin, co-founder of Hexlet (one of the largest programming schools in the Russian-speaking world), made for his Russian-speaking developer audience. Almost all the stars came from his own channels: the Telegram channel @orgprog (16k subscribers) drove the first wave, and a dedicated YouTube podcast episode (about 40k views) drove the second. The product's edge is "one recommended tool per category + the build must be able to fail + one sentence makes the agent wire the list into your repo." That makes it easier to actually use than a typical awesome list, but it took off mainly because the author brought his own audience. It also serves as top-of-funnel content for Hexlet's course "AI for Developers 2.0."

### What it is

- An **opinionated** tool list (CC0): organized by language (JS/TS, Python, Go, Rust, Ruby, PHP, JVM, .NET, Elixir, and more) and cross-cutting categories (GitHub Actions, GitLab CI, Markdown, OpenAPI, containers, architecture dependency rules, migration safety, and so on). For each job it recommends only 1 tool (occasionally 2), and states what it does and its limits. The README is generated from `tools.json`, and every tool records a review date and source. The repo has a GitHub Action that regularly produces a "tool freshness report" (issue #20), flagging entries that are 90 days or older for re-review (PR #22). Sources: [README](https://github.com/mokevnin/dev-quality-gates), [issues/PR lists](https://github.com/mokevnin/dev-quality-gates/issues).

- The principles are stated firmly: "Enforcement over advice" (must fail the build with a non-zero exit code), "Agent-friendly" (non-interactive, machine-readable output, safe to auto-fix), "Fast native toolchains first" (prefer Rust-native tools like Ruff, Oxlint, and Mago), and "Honest about gaps" (leave a slot empty rather than recommend something outdated).

- **The key usage:** the README includes a prompt you can paste directly to a coding agent: "Apply [github.com/mokevnin/dev-quality-gates](https://github.com/mokevnin/dev-quality-gates) to this repository. Read and follow …/docs/adopt.md. Show me the plan before you change anything." The agent then inspects the project, picks the right entries, wires them into hooks and CI, and "proves every check can fail." This paragraph was added in PR #12 by 10-25.

- The repo was once called `dev-guardrails`. Issue #2071 in hexlet-volunteers/hexlet-sicp (10-26) still references `mokevnin/dev-guardrails`, from before the rename to the current name.

### Growth curve and matching events

| Date | Stars (GitHub repo_day / data card) | Event |
|---|---|---|
| 10-23 22:48 UTC | 0 | Repo created |
| 10-24 13:00 UTC | — | Telegram @orgprog post #534 "Quality Gates всем и пусть никто не уйдет обиженным," with the repo link; about 7K views and about 157 reactions ([t.me/orgprog/534](https://t.me/orgprog/534), scraped 2026-11-06) |
| 10-25 | 42 | Added the "paste one sentence to your agent" setup instructions (PR #12); people from the Russian developer community began opening PRs (savinmikhail, strelov1, solar05) |
| 10-26 | 97 (single day +55, highest during the observation period) | The post kept spreading; the same day, the Hexlet volunteer project hexlet-sicp opened a refactor issue based on this list; a Nigerian developer on LinkedIn included it in a roundup of "3 open-source AI repos this week" ([link](https://www.linkedin.com/posts/mriridescent_ai-opensource-softwareengineering-activity-7520160047293800448-1zT-)). Which repost drove this day's peak is **unverified** . |
| 10-27 to 11-01 | 120 → 165 | Natural decay, +3 to +17 per day |
| 11-01 14:50 UTC | — | YouTube podcast "Organized Programming" solo episode "How to Control AI Agent Code: Quality Gates, Architecture and Developer Tools", ~39.7k views (Jina scraped the YouTube page, 4 days after publishing); also posted to TG (#538,6.1K views), X (2,182 views), LinkedIn, Apple Podcasts |
| 11-02 to 11-05 | 182 → 293(+128) | Second wave, lines up with the video release |
| 11-06 | 299 |  |

Also checked: Hacker News has no record of this repo; searching the local x-radar corpus for `dev-quality-gates` and `mokevnin` returns 0 hits each (the author is not in the five circles we track). It has barely spread in the English-speaking world.

### Competitors

| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| analysis-tools-dev/static-analysis | Open source | 2015-12 | 14,874 stars | An exhaustive list of hundreds of SAST tools and linters; no opinions given, and no "plug it into CI" workflow |
| caramelomartins/awesome-linters | Open source | 2014-02 | 1,108 stars | A community-maintained awesome list; old, comprehensive, no curation |
| super-linter | Open source / GitHub Action | 2019-10 | 10,650 stars | Bundles a pile of linters into one Action that runs them all; it's a runner, not a selection guide, and isn't aimed at agents |
| MegaLinter | Open source | 2020-10 | 2,647 stars | Same idea, covers 50 languages, takes the "turn everything on" approach, the exact opposite of this project's "pick just one" |
| qlty | Open-source CLI + SaaS | Built as 2015, later renamed to its current name | 3,217 stars | A unified lint / format / security CLI with a paid cloud offering |
| Trunk Check | Commercial | Around 2022 | Not verified | A commercial unified linter manager |
| SonarQube / Qodana quality gate | Big-company features | Years | Enterprise | Quality gates and metrics inside a platform; paid and report-oriented, not a lightweight combination of tools that fail the build |
| pre-commit / lefthook | Open source | 2014 / 2019 | 15,686 / 9,001 stars | A hook manager that only handles how checks run, not which tools to pick; this project instead recommends tools like lefthook and mise |
| amElnagdy/guard-skills | Open source | 2026-06 | 1,310 stars | A quality gate in agent-skill form that catches failure modes specific to AI-written code; it's a prompt layer, not a deterministic toolchain |
| soumatheusgomes/vibe-coding-toolkit | Open source | 2026-08 | 2,286 stars | A large Claude Code plugin + quality gates + prompt bundle, leaning toward "give you everything" |
| shadcn-ui/lint | Open source | 2026-09 | 3,315 stars | A single agent-first linter (Tailwind design system); it's one tool, not a selection list |

(Competitor star counts and creation dates come from the GitHub API and our github database, 2026-11-06.)

Takeaway: "linter checklists" and "linter aggregation runners" are mature, long-established categories, with top repos at tens of thousands of stars; "AI agent quality gates" is a topic that emerged in the last 2026 years, and several repos already have thousands of stars. This project carves out a small niche where the two overlap: **an opinionated curated list + adoption instructions written for agents to read** .

### Growth tactics (where users come from)

1. **The author's own Russian-language channels** (confirmed): TG @orgprog with 16k subscribers, where a typical post gets 4K–10K views; YouTube podcast episode with 40k views; also cross-posted to X (@mokevnin) and LinkedIn. The two star-growth waves line up with the TG post at 10-24 and the video at 11-01.

2. **Adopted inside the Hexlet ecosystem** (confirmed): hexlet-volunteers/hexlet-sicp opened an issue to rework itself per the checklist; students' or community members' repos (mbylinkin/currency_exchange #43, mbylinkin/hangman_game #22) opened "Adopt Dev Quality Gates" issues. This shows people really are using the "paste one line to the agent" approach.

3. **Community contributions** (confirmed): about 6 external contributors opened PRs in the first week (mostly Russian-speaking developers), plus several forks. Many contributors make a repo look active and more trustworthy.

4. **Sporadic English-language pickup** (partly confirmed): one LinkedIn post, a roundup of "new open-source repos this week", mentioned it; found no coverage on HN, Reddit, major X accounts, or media.

5. **Business loop** : the footers of the TG posts and videos link to Hexlet's course "ИИ для разработчиков 2.0" (4–5 weeks, covering agent programming, verification loops, and SDD), along with a link to "Системный дизайн". The author 10-18 posted that he will personally lead the first cohort. This repo is the course's public sample and lead-gen content, and the money comes back from the course.

### Why it's working

- The author brings his own distribution: co-founder of Hexlet, 1,343 GitHub followers, 16k TG subscribers, and YouTube podcast episodes that each get tens of thousands of views. Both star-growth waves correspond to content he posted himself.

- The topic hit at the right time: in the second half of 2026, "how to constrain the code agents write" was a hot topic (the author's own TG has discussions like DHH's "hand-writing code isn't worth it anymore"; on GitHub, similar guard / quality-gate repos kept appearing from 6 through September).

- Immediately usable: it's not just a list, but a prompt you paste into Claude Code / Codex plus `docs/adopt.md`, so readers can get it running in their own repo the same day they read it. Real adoption records are visible in the issues.

- Credible: every tool has a review date, a research doc, and a reason for exclusion (e.g. React Doctor and deadcode were evaluated and not included), plus automatic freshness checks. This contrasts with awesome lists that include everything.

### Differentiation, and whether it's why it took off

There are three points of differentiation: (1) **each category recommends just one tool** , with its limitations spelled out; better to include nothing than something weak. (2) **the inclusion criterion is "can make the build fail, and is agent-friendly"** , not "if it's a linter, it's in". (3) **the checklist itself is written for agents to read** : one prompt gets an agent to adopt it, and every check must be shown to be able to fail. These differences are why it **holds people's attention and gets actually used** (external PRs and adoption issues within the first week). But **the reason it took off is mainly the author's audience and course funnel** . The absolute numbers are only 300 stars, concentrated in the Russian-speaking world, which shows that differentiation alone didn't make it spread in the English-speaking world.

### Visibility

- It's circulating in small circles: Russian-speaking developers (TG, YouTube, the Hexlet community). The English-speaking world barely knows about it: 0 HN posts, 0 on x-radar, and only one small-account roundup on LinkedIn found.

- Revenue: the repo itself charges nothing; the Hexlet course behind it is sold publicly (and the course has already shown up on pirated course sites, which suggests it has some demand).

- Copycats: haven't seen any new repos copying this format yet; only ordinary forks (redb0, solar05, sub4biz, etc.) and adopters.

### What others can borrow

- The "checklist + adopt.md for agents + one-line prompt" format: it turns a content repo into an "installer" an agent can execute; readers can use it immediately, and adoption leaves issues and links in other repos, bringing secondary exposure.

- Separate from awesome lists by being "opinionated + dated reviews + stated reasons for exclusion".

- Content (repo) → personal channels (TG / podcast) → course monetization, each feeding the others. This path assumes you already have an audience; someone copying the format without one is unlikely to reproduce this growth curve.

- Doing the same "agent-executable curated list" in a different language community or vertical (e.g. mobile, data engineering, frontend design systems) is still an open gap.

### Unknowns

- The specific source of the 10-26 single-day +55 spike: whether it was the long tail of the TG post or a forward from another channel, is unverified.

- Geographic distribution of starrers: the GitHub stargazer API couldn't be queried with our token, so no sample was taken; the claim that it "mainly comes from the Russian-speaking world" is based on channels, contributors, and adopters, and is not directly verified.

- How much the course converted is unknown.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.