agentos.guide › blog
Grok Bot Plugins In Your Agent OS: Quick Start, 5 Copy-Paste Prompts And A Weekly Workflow
Grok Bot plugins slot into your Agent OS as the app layer: your agent briefs the Bot, the Bot works inside Gmail, Notion, Slack or Linear through its plugins, and you approve anything that leaves the building.
Since v0.71.2 (14 October 2026), a single Bot can call on up to 200 skills from installed plugins rather than 24.
Below is a quick start, five copy-paste prompts and a weekly workflow.
Want help fitting this to your own operation? Book a free SEO strategy session with my team.
Why a plugin register beats memory
Plugins pile up quietly, and nobody remembers which account each one was signed in with.
That matters because a connected app is available to every Bot on your account, not just the one you set it up for.
A register in your Agent OS fixes this with one row per plugin.
Record the app name, the signed-in account, the skills it brings, the Bot that uses it most and the date it was last checked.
Add a column for the approval rule that applies, so nobody has to guess whether a send needs sign-off.
With the cap now at 200 skills per Bot, the register is also how you spot plugins you no longer need.
Uninstalling those keeps the Bot's choices narrow and its behaviour predictable.
Treat the register as the source of truth and the Connect apps screen as the thing you check it against.
Your Agent OS agent can keep it tidy: ask it to compare the register with each weekly audit and flag any drift.
Quick start: three moves before your first prompt
- Check your plan: Grok Bot is on Premium, Super and Ultra; Plus doesn't include it.
- Open Connect apps in the sidebar and add the one app your agent touches most.
- Confirm it sits under Installed and doesn't show Needs auth.
Plan names come from the X Subscription page.
Added only means installed, so the sign-in check is the step people skip.How the pieces fit together
| Layer | Job | Where it lives |
|---|---|---|
| Agent OS | Plans the work, keeps the plugin register and skill specs | Your dashboard |
| Grok Bot | Runs the task on its cloud computer | Grok Bot app |
| Plugins | Structured tools for each service | Connect apps, account-wide |
| Skills | Saved instructions, up to 200 from plugins | Private skills library |
Plugins are account-wide, so every Bot you run sees the same set.
OAuth tokens stay on Cursor's connector backend, per the computer and apps docs, and the Bot never receives them.
That's why the register in your Agent OS should record which account each plugin is signed in with.
Prompt 1: audit what's already connected
Paste this into a fresh Bot chat first. It gives you a baseline.
List every app installed on my account under Connect apps.
For each one, tell me: the account it is signed in with,
whether it shows Needs auth or Disconnected, and which
skills it adds. Then flag any app I haven't used in a task
this month so I can decide whether to keep it.
Return it as a table.Copy the table into your Agent OS as the plugin register.
Prompt 2: install a plugin the fast way
Add the Notion app. If it isn't installed, check the plugin
catalogue and give me the Connect card. Once I've signed in,
confirm it shows under Installed and run one read-only test:
list the five most recently edited pages I can open.Since v0.77.0 the Bot checks the catalogue itself when an app is missing.
Since v0.75.8 it can use the new plugin's skills straight away, mid-task.
🔥 Get the Agent OS that briefs your Bots for you
Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running agent crews like this one.
Prompt 3: turn a clean run into a skill
The skills and routines guide lists six parts every useful skill states.
This prompt asks for all six.
Save the process we just used as a skill called
"Weekly client digest". Include: when to use it, the apps
and logins it needs, the sequence of steps, how to check the
result, what to return, and the rule that anything sent to a
client needs my approval first. Keep it under 300 words.Private skills form one library shared by all your Bots.
If a Bot can't find it, enable it under Private skills from the connected count in Connect apps.
Prompt 4: set the approval boundary once
Remember this as a standing rule for every plugin you use:
ask me first before you send, post, delete, buy, publish or
change a production system. Drafts and read-only lookups can
go ahead. If I deny an approval, stop and wait for my next
message.The Grok Bot FAQ recommends exactly this kind of narrow Ask first rule.
Since v0.75.5, a denied approval card stops the Bot until you send another message.
Prompt 5: add a server that isn't in the catalogue
Add this MCP server for me: <server URL>.
Tell me whether it's on a private network or uses a private
certificate authority before you connect it, and wait for my
approval if it does. Then list the tools it exposes.Your Bot accepts either a web address or a launch command for the server.
Launch it by command and every Bot on your account can reach it afterwards.
The weekly plugin workflow
- Monday: run Prompt 1 and update the plugin register in your Agent OS.
- Tuesday: install one new plugin with Prompt 2, only if a real task needs it.
- Wednesday: run the task once, then save it with Prompt 3.
- Thursday: turn the skill into a routine and press Test with safe inputs.
- Friday: review drafts, check usage, and pause any routine that ran more than it needed to.
Routines run up to 300 times an hour across your account and 200 an hour per routine.
A busy Slack trigger can burn a week of usage in a day, so keep triggers narrow.
📞 Want your plugin stack planned for you?
Book a free SEO strategy session and my team will map the apps, skills and approvals that fit your business.
When a plugin stops working mid-week
Most breakages are sign-in problems, not plugin problems.
Start with the status in Connect apps: Needs auth or Disconnected means choose Authenticate, or Authorize on the phone.
If a routine hit a signed-out connector, v0.75.2 drops a Reconnect card in chat, at most once a day.
If a company Google account blocks the sign-in with “Your admin needs to review Grok”, your IT admin has to set the app named Grok to Trusted in the Google Admin console.
Swapping browsers won't clear that block.
Don't remove and reinstall a plugin as a quick reset: removal signs you out and deletes everything the app added.
Log each fix in the register so the next failure takes minutes, not an afternoon.
One of my plugins has stopped working. Check Connect apps
and tell me its status, the account it uses, and the last
task that used it successfully. Suggest the least
disruptive fix first, and don't remove the app.If your Agent OS runs on a Cursor team
Teams add a policy layer above your prompts.
Grok Bot inherits the team's Cursor connector policy, and blocked apps show Disabled by team admin.
Admins can't push connectors onto members, so each person still installs their own.
The MCP allowlist is Enterprise only, and remote MCP servers need Apply to MCP servers switched on to follow the network allowlist.
A shared Bot keeps its own Plugins, Secrets, Skills and Files, and asks before it touches a teammate's personal accounts.
Record in the register which plugins belong to the shared Bot and which belong to individuals.
Gotchas worth writing into the register
- Gmail connects one mailbox at a time.
- Calendar can't add a Zoom link via Google's add-on; Zoom authorisation on desktop currently fails with error 4700.
- The X plugin needs X API credits on your X developer account.
- Removing an app signs you out and removes everything it added.
- On a team, blocked apps show Disabled by team admin, and blocking an app doesn't block its website.
Team rules sit in the teams and enterprises docs.
For the full Agent OS setup with trainings, join the AI Profit Boardroom.
Prefer a call? Grab a free strategy session and bring your plugin register.
Also On Our Network
- 🌐 The four-step install order plus every per-app gotcha in the docs
- 🌐 Three small-business setups and the risks to plan for first
- 🌐 An eight-criterion scorecard with a 7.8 overall rating
- 🌐 Real GoldieBench scores and which models to route around the Bot
- 🌐 The complete Grok Bot Plugins guide on the AI Profit Boardroom blog
FAQ
What should my first Grok Bot plugin prompt be?
An audit of every installed app, its signed-in account and its status. It gives you a baseline register before you add anything.
Where do saved plugin skills live?
In one private skills library shared by all your Bots. Enable a skill for a specific Bot under Private skills in Connect apps.
How do I stop a Bot acting on a plugin without me?
Give it a standing Ask first rule for sending, posting, deleting and buying. A denied approval stops the Bot until your next message.
How often should I review my plugins?
Weekly. Re-run the audit prompt, update the register and pause routines that ran more than they needed to.
Final word on Grok Bot Plugins In Your Agent OS
Paste Prompt 1 into a Bot today, file the answer in your Agent OS, and book a free strategy session if you want a hand planning your grok bot plugins.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
Related guides on agentos.guide
→ Best Hermes Agent Plugins: My Top 10 For An Agent OS
→ Grok Bot Routines: Plan And Review Them In Your Agent OS
→ Grok Bot Slack: Run A Shared Team Bot In Your Agent OS
→ Hermes Agent Plugins Marketplace: 5-Step Quick Start
Get the whole Agent OS
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉