ECOSYSTEM

How the 284 is made up: 126 catalogued at grokbot.dev, each with a prompt you can copy, plus 108 in the thread that started all of this, plus 50 published in the field. 11 appeared in two of those lists and are counted once. Filter the table by source and the three numbers appear on their own.

Not inside that total, and further down the page: 28 repositories opened and read today, and 27 bots on a network only bots can write to.

Jobs

Everything anybody has published about giving a Grok Bot real work, from three sources, in one table. The source column says where each line came from, and every line links to it.

Only the grokbot.dev lines carry a category, because only that source assigns one. Filtering by category narrows to those rather than inventing categories for the rest.

People

112 people are named on this page. Every one of them published the work themselves. This table is the whole reason the page exists: the jobs column counts what they published, the projects column counts what they built.

Projects built on top

Things that exist because Grok Bot exists. A social network only machines write to, a software factory living inside one Bot, a trading desk of seven, a directory that is itself a Grok Bot. Every link opened on 2026-08-27, every owner confirmed on their own post.

One of them, measured from its own stats endpoint on 2026-08-27: 27 verified bots, 25 hosted pages, 321 board posts of which 319 in the last 24 hours, 4 channels.

Plugins in the marketplace

219 plugins across 13 categories, and none of them arrives installed. This is the marketplace inside Settings, from a public directory of it captured on 2026-08-12. Search it, or filter by what you actually need.

Code you can install

Every repository named anywhere in the ecosystem, opened on 2026-08-27 with its star count read off the counter on the page. An archived repository says so, because an archived repository still has stars.

28 repositories, every one opened today. Stars are read off each page rather than from an API, because api.github.com answers 403 from a shared address and a rate-limited API is not a source.

Four things people call the same thing

Most arguments about what a Grok Bot can do are two people describing different products. These are four, and only the first is a Grok Bot.

Read this page with your Grok Bot

All of it is on /ecosystem.json: every job with its source, every person, every project, every repository with its star count and the timestamp of the read, and a block saying how each number was reached.

Every morning, fetch https://nowmode.app/ecosystem.json.
Compare it with the copy you kept yesterday.
Tell me only three things:
  1. jobs or projects that are new since yesterday
  2. any repository whose star count moved more than 10 percent
  3. any new plugin in a category I use
If nothing changed, say nothing changed. Keep today's copy for tomorrow.

The same trick works on grokbot.dev/agent, which publishes a contract for exactly this and is where 126 of the jobs here came from.

Where this comes from

Three sources, all public, all linked from every row that came out of them.

grokbot.dev publishes 126 jobs with a copyable prompt each, through a JSON API and a written contract for bots. @ericzakariasson published 108 of them on X, in his own words, read here post by post. The remaining 50 were published by the people who ran them, and every one of those posts was opened before it went on this page: 29 distinct posts, 0 with an author who did not match, 0 missing.

Nothing here is typed by hand. One script re-reads every source and writes the answer with the time of the read attached; another renders this page from that file alone, so no figure can quietly go stale. Anything that could not be read says unknown. The full audit, including what each number was checked against, is in the JSON.