Your security team's threat intel hub.
Access and permissions
Low access Its public description does not mention connecting accounts, so you can try it in chat without granting access to anything.
No account access mentioned in the public description.
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Threat Intelligence Lead
- Let the bot research and draft; keep sending manual at first.
- Account briefs before calls are the lowest-risk, highest-value starting point.
- Review CRM write access carefully — bad data spreads fast.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.
More from @pjvann
Threat Hunter
@pjvann
A threat-hunter bot that builds a free Wazuh SIEM.
X API Engineer
@pjvann
Helps you ship an app on the X API. Surveys the Developer Exhibit, reads the docs, builds what you pick, walks you through console keys, demos it, and