Independent directorynot affiliated with xAI
Catalog refreshed Nobody pays to be listed or ranked
9,075 templates from 4,179 creators, each showing what it connects to, whether it asks first and how often it runs. “Checked” means the link was reachable — not a safety rating.
Point this bot at the repositories you want covered and it takes over the checkpoint every pull request has to clear. It holds off until your test pipeline and an automated bug revie…
This one holds the thinking end of a coding setup and is deliberately kept off the keyboard. It works out what a task really requires, argues with the approach until it stands up, an…
Built for developers who watch a week's allowance disappear by Tuesday. It stands up separate working seats on the computer it controls, then pushes the long grinding tasks out to th…
A reference desk for the Grok Bot application itself. Instead of replying from a training snapshot that may have aged badly, it inspects which extensions and integrations exist and w…
This one hands the actual xAI command-line coding agent a computer of its own, so you can point it at an app you want built, a code change you need made, or a long research question,…
Sidebar commands for looking after the cloud Linux machine your bot runs on. Ask for a health readout and it reports processor load, memory pressure and free storage; a separate comm…
Built for the moment right after signing up, when nothing is plugged in yet. It asks what you do and which software you already lean on, gets the relevant integrations authenticated…
Building a bot badly means a bloated brief and responsibilities scattered anywhere they happen to fit. This writes a short, sharp character for each new one and sorts every duty deli…
This bolts durable recall onto Grok Bot by parking your running context in an outside memory service. Before answering it checks what has already been filed about your job, your life…
Two jobs in one companion for developers. It queries the Australian public registries for company numbers, regulator filings, registered addresses, bank codes and the rest, and it wa…
This one exists so a collection of assistants never ends up stranded where it was first built. It keeps a current register of every bot you run, the skills each carries, what it plug…
Think of it as a removal service for an assembled team of assistants. It takes stock of who is on the roster, gathers what each one carries — its remit, what it has picked up, the ti…
Some documents cannot reasonably be pasted into a general assistant, so the analysis simply never gets done at all. This carries out the work inside a sealed hardware enclave instead…
For analysis that outgrows the machine in front of you. It sources the graphics hardware you need from Prism Network's marketplace, hands your workload across to it, and brings the o…
For work where being confidently wrong is expensive. Every question goes to Grok's most recent model with web lookup left switched on, so answers arrive attached to the pages they we…
A build partner for teams working on The Graph's Substreams stack. It searches the public package index for existing modules worth reusing, wires them together for you, then helps yo…
Some work simply will not sit on a machine you are sharing: a kernel that wants real silicon, or a fault that shows itself only under CUDA. Hand the job across and it secures hardwar…
It keeps a register of the standing jobs your bots run, noting how often each one triggers and what that cadence costs you. Anything spending more than it returns gets flagged, and c…
A build-and-maintain helper for one niche hardware hookup: getting readings off a Ubiquiti air-quality sensor and onto a small always-on e-ink screen. It scaffolds the private displa…
This one stays deliberately small: rather than doing the engineering itself, it passes each job out to a command-line coding tool you already pay for. Cursor is the standard target,…
Keeps a short, stable record of how your work actually fits together: what you do, what you are aiming at, who matters, how your tools are set up, and which calls are already settled…
A strategist for problems where the conventional answer feels thin. It first states plainly what a competent specialist would recommend, then searches unrelated fields for a cheap, u…
Sits above a two-tier setup where Grok bots handle the thinking and Mac command-line tools do the executing. Work is sorted into separate research and coding rooms, briefs that misse…
Once you are running more than a handful of agents, some duplicate each other and some quietly stop earning their place. This one reads across the whole roster, flags the overlaps an…
If you already pay for Claude Code or Codex, this lets you drive those coding sessions from a Grok conversation instead of living in a terminal. Kick off a task, watch it progress an…
Acts as the deputy when work is spread across several AI services: it holds the project record everyone works from, checks that each handoff actually happened, and pushes back when a…
Works a layer up from your Cursor cloud coding agent and owns the thinking rather than the typing: running a GPT-6 Astra session inside Codex CLI, it produces structured PLAN and REV…
You describe a fuzzy problem and it comes back with a design: either one tightly scoped bot or a small team of them, each with a defined job. Work is staged from simple to ambitious…
Feed it a single idea, or a chore you keep repeating every day, and it drafts the entire bot around it: the concept, a quick market scan, the persona, the skills, the routines and ev…
When bots start working at cross purposes, usually because a prompt was too vague, it runs the check-ins, works out who misunderstood what, and proposes repairs you can apply. Regula…
Point it at the bots, skills and routines already running in your workspace and it reviews what each one does with your data. It hunts for outbound calls nobody mentioned, quietly co…
One bot owns the browser and the rest of your team can use it, so pages, sessions, and logins stay in one place instead of being rebuilt per task. Its interface is aimed at awkward s…
Converts messy bug threads into repro packs an engineer can trust: it walks the same path the reporter took, in staging, captures the moment the failure actually fires, and packages…
Built for a phone on an active civil site: photograph a problem and it produces a structured card describing the issue, with a draft RFI to match. The package is emailed to you so th…
Give it a public page, an essay, or a playable demo and it reads the way a stranger would, knowing nothing about the project beforehand. It reports the exact spots where a newcomer s…
Built for a questline-graph product where several coding agents work in one repository. It carries the project's standing conventions, which layer is the source of truth, how the res…