Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add notforyou23/home23 --skill xai-x-searchgit clone --depth 1 https://github.com/notforyou23/home23Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/notforyou23/home23/xai-x-search)<a href="https://agentmods.dev/skills/notforyou23/home23/xai-x-search"><img src="https://agentmods.dev/badge/skills/notforyou23/home23/xai-x-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/notforyou23/home23/xai-x-search"><img src="https://agentmods.dev/badge/skills/notforyou23/home23/xai-x-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 111 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00859 |
| Opus 5 | $0.00016 | $0.00430 |
| Sonnet 5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
xAI X Search scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
xAI X Search
Search X/Twitter through Grok's native x_search server-side tool via the xAI Responses API. This does not use the X developer API — it uses the xAI API key already configured in Home23 secrets.
When to use
- "what are people saying on X" questions
- live discourse around topics, products, people, events
- checking recent posts from specific accounts
- following a thread from a tweet URL
- any X/Twitter research when the X developer API is unavailable or out of credits
When NOT to use
- Posting, replying, or authenticated account actions → use the
xskill - Raw tweet JSON / structured data extraction → use
x-research(X developer API)
Actions
search
Search X in real-time. Grok searches natively and returns a synthesized answer with citations.
Input:
{
"query": "what are people saying about AI agents",
"fromHandle": "elonmusk",
"excludeHandle": "spamaccount",
"fromDate": "2026-07-20",
"toDate": "2026-07-23",
"model": "grok-4.5"
}
query(required): Natural language question or search topicfromHandle(optional): Only include posts from this X handleexcludeHandle(optional): Exclude posts from this X handlefromDate/toDate(optional): ISO 8601 date range (YYYY-MM-DD)model(optional): xAI model to use (default: grok-4.5)
thread
Fetch and summarize a conversation thread from a tweet URL.
Input:
{
"url": "https://x.com/user/status/123456789",
"model": "grok-4.5"
}
profile
Read recent posts from a specific X account.
Input:
{
"username": "elonmusk",
"model": "grok-4.5"
}
How it works
- Sends the query to the xAI Responses API (
/v1/responses) withx_searchenabled as a server-side tool - Grok searches X natively in real-time
- Returns a synthesized answer with citations to the original posts
- Optional parameters filter by handle, date range, and media understanding
Gotchas
- This returns synthesized answers with citations, not raw tweet JSON
- Grok decides what's relevant — results are curated, not exhaustive
- The xAI API key is in
config/secrets.yamlunderxai.apiKey - Rate limits follow the xAI API plan, not X developer API tiers
- Image/video understanding can be enabled but increases token usage
- For structured data needs (metrics, exact timestamps, bulk export), use
x-researchwith the X developer API instead
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 114 lines · 33 tokens per session scan A ecb2a67fdf48
xAI X Search is a skill published in the GitHub repository notforyou23/home23 (11 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 859 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
industry-intelligence-radar
An industry-monitoring workflow that scans sources such as Hacker News, V2EX, RSS feeds, X, and 即刻 for selected keywords and trends.
codex-grok-search
MUST use first for current X/Twitter or Reddit searches, including latest posts, recent discussions, community sentiment, platform data collection, and cross-platform research. Bridges Codex to the user's locally authenticated Grok Build from a private directory outside the current project, saves Grok's complete…
xpoz-social-search
Search Twitter, Instagram, and Reddit posts in real time. Find social media mentions, track hashtags, discover influencers, and analyze engagement, with billions of posts indexed. Social listening, brand monitoring, and competitor research made easy for AI agents.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…