Price terms as published
Each line is the vendor’s own wording, split from the price capture checked on 2026-10-28. Nothing here is rounded, converted or re-worded — the full sentences stay in the review below. Lines that carry only a price continue the plan named on the line above, in the vendor’s own order.
| # | Plan / term | Checked |
|---|---|---|
| 1 | Included with Grok Premium $30/mo, Super $100/mo, Ultra $200/mo | 2026-10-28 |
One-liner: A Grok Bot template turns a working bot into a link somebody else can add as their own copy in two clicks — the configuration travels, the author’s private memory does not.
Evidence level: official terms and documentation plus live public template pages, all fetched 2026-10-28. We did not install Grok Bot or run a bot, so nothing below is a hands-on claim.
What a template actually is
xAI’s own template guide describes a template as “a collection of skills, memories, and plugins” and calls it “a recipe, not a meal” — the recipient gets the setup, then feeds it their own work. The official walkthrough says the packaging step reads through the bot’s memories, skills, routines and plugins and assembles a template from them.
The important consequence is that sharing a bot and giving someone your bot are different things. xAI’s documentation says the link does not give the recipient your computer, your logins or your conversation history. What it does expose is the configuration itself — the same docs warn that the link exposes the bot’s configuration, which is why the author-side checklist below starts with stripping secrets.
How to publish a template
This is the part where most second-hand write-ups go wrong. There is no submission queue for templates: you publish from the bot, and the result is a link.
- Open the bot in Grok Bot and go to its settings.
- Choose Share as Template (the button sits in the bottom-right of the settings panel).
- Grok Bot prepares an anonymised draft from the bot’s configuration. Nothing goes live at this point — the guide is explicit that clicking the button does not make the bot public.
- Pick the audience: Team for a team-only link, or a public link. Enterprise accounts default to Team-only; everyone else defaults to a public link.
- Click Publish and then Copy Link. The template page is now viewable at that URL, and the bot’s own share menu offers View template details and Update template afterwards.
- Before sharing widely, strip API keys, internal URLs and anything a stranger should not have, and write down the setup steps a recipient has to do by hand — the parts that do not travel (next section).
For a whole team rather than one link, the docs describe a separate Publish to Team action that makes the bot part of the shared team library.
How to install a template, and how to vet it first
Installing is deliberately short, and the approval step is where the safety lives:
- Open the template link. It resolves to a preview page on
x.aithat names the bot, its author and what it does. - Read the two warnings on that page. Every third-party template carries: “This AI bot was created by a third-party user, not by SpaceXSI. It may act on your behalf.” and adding it accepts the bot-sharing terms.
- Choose Add to Grok Bot. The app opens a review screen showing the context and the first-party integrations or skills the template wants, then Add Bot creates your own copy.
- Treat the copy as someone else’s recipe with your permissions attached: it can use your signed-in tools, so review what it is allowed to touch before you give it a real task.
A practical vetting rule when the template is token-hungry or touches money, mail or publishing: install it, ask it to describe its own plan for a small task, and only then grant it a real one. Templates that were built well ship a first-run playbook for exactly this — the public Forge template asks the recipient to fill placeholders before it will produce anything, and loops refuses to guess which repo it should work in.
What a template does not carry
The gaps are the reason a template sometimes looks broken when it arrives. From xAI’s guide, a template does not include:
- Private memories. Personal and internal memories stay with the author. The recipient’s copy starts without the context that made the original good.
- Custom plugins, MCP servers, scripts and code. If the bot depended on one, the recipient installs it separately. The guide’s own example template for a coding workflow attaches CLI setup instructions as downloadable files — that is the pattern: ship the instructions, not the binary.
- Anything secret. Credentials, keys and internal endpoints have to be stripped. A template that leaks them is a security incident with a friendly preview page.
So the honest mental model is: a template is a well-written onboarding document plus a configuration. Whatever the recipient cannot read, they cannot reproduce.
What it costs
Templates themselves are not sold. There is no per-template price and no fee to publish one; the cost is the Grok Bot plan, and templates ride on it.
| Plan | Price | What it includes | Source |
|---|---|---|---|
| Premium | $30 / month | Grok Bot’s own computer, signs into your tools, scheduled routines, weekly usage | x.ai/bot pricing, 2026-10-28 |
| Super | $100 / month | Everything in Premium, 3.5× Premium usage, priority model access at peak times | same |
| Ultra | $200 / month | Everything in Super, 12× Premium usage, earliest access to models | same |
| Teams / Enterprise | Contact sales | Grok Bot is included for eligible existing plans | same |
Two footnotes the pricing page states itself: subscriptions include weekly usage with additional usage billed at token cost, and every Grok Bot on one account shares a single persistent cloud computer (isolation is per user, not per bot) — which is worth knowing before you install a template that has broad tool access.
The client runs on macOS and Windows desktop plus an iOS app, and the download currently ships an Apple-silicon macOS build from Cursor’s update server; the FAQ says it uses the same Cursor SSO and privacy mode. If you have never used Cursor, expect a parallel account setup rather than a Grok login.
How this compares with other ways to share an agent setup
| Mechanism | What the recipient gets | Review by the vendor? | Best for |
|---|---|---|---|
| Grok Bot template link | Skills, memories, routines and plugin references, as a copyable configuration | No — publishing is self-serve | Handing a working setup to a colleague or an audience |
| Grok Bot Marketplace listing | A curated listing in the app sidebar that users can add | Yes, xAI curates what is listed | Getting distribution to strangers |
| Plugins and MCP servers | A capability the bot can call, installed separately | Yes — submitted through x.ai/bot/marketplace/submit-a-plugin and reviewed |
Shipping a tool, not a workflow |
| Prompt in a blog post or thread | Text the reader pastes and adapts | No | Teaching a method to people who will rebuild it anyway |
The distinction that matters in practice: templates are shared, plugins are submitted. If your question is “how do I get my template into the official Marketplace”, the answer is that the Marketplace is xAI’s curated shelf, and the self-serve submission path exists for plugins and MCP servers — not for templates. Sharing a template is instant and unlimited; getting listed is a curation decision you cannot self-serve.
Templates that are public today
Nine public template pages resolved and named an author when checked on 2026-10-28. Two links circulating in a community roundup were already dead, which is worth knowing if you are assembling a directory of these.
| Template | Author | What it does | Link |
|---|---|---|---|
| loops | Matt | Engineering outer loop above coding agents: gather, prompt, launch, review, merge | x.ai/bot/Ub3T7usX… |
| DOGE (Department of Grok Efficiency) | Avid | Audits your other bots and routines, flags what to cut or merge, changes nothing without approval | x.ai/bot/d8OshqLZ… |
| Forge | Robert | Turns one keyword or job description into a production-ready bot recipe | x.ai/bot/uF_uodOF… |
| Master | Farzad | Lean orchestrator for a creator or media team; routes work, pings only when needed | x.ai/bot/j7B5LHnE… |
| Growth Desk | Avid | Draft-only X growth desk: scores one named account, drafts, and holds everything for approval | x.ai/bot/YYCOE-Ye… |
| Grok Bot Coach | Amina | Weekly audit of a bot set — setup, safety, credit use — with fixes proposed per bot | x.ai/bot/BrjELcmS… |
| the j*bfinder | Daniel | Job and internship search: keeps a Notion application tracker current from recruiting email | x.ai/bot/eSCwViGd… |
| club events ops | Daniel | Student-club paperwork: weekly due-date reminders, funding and venue forms, Notion event list | x.ai/bot/SDLUUiG6… |
| Shopper | Pete | Researches purchases across signed-in stores, returns top 2–3, waits before buying | x.ai/bot/–X3KeUB… |
What the list shows is the shape of the early ecosystem: engineering orchestration, self-auditing meta-bots, personal admin, and shopping. What it does not show is a marketplace of paid templates — there is no pricing mechanism to build one on yet.
Verdict
If you already pay for Grok through Premium, Super or Ultra, Grok Bot is included and a template link is the cheapest way to hand someone a setup that actually runs. Publish one if you have a workflow worth repeating and can write the missing-steps document; install one if you accept that a third party’s recipe runs with your tool access, and read the preview page rather than the tweet that linked it.
If you are waiting for a template marketplace with categories, rankings and a submission form, that is the wrong mental model — sharing is a link, and the only reviewed surface is plugins and MCP servers. Build for the link, and treat the Marketplace listing as xAI’s call, not yours.