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-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-search)<a href="https://agentmods.dev/skills/notforyou23/home23/xai-search"><img src="https://agentmods.dev/badge/skills/notforyou23/home23/xai-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-search"><img src="https://agentmods.dev/badge/skills/notforyou23/home23/xai-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 62 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.00000 | $0.00634 |
| Opus 5 | $0.00000 | $0.00317 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
xai-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 11d 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 Search
Search X/Twitter and the web using Grok's built-in search tools via the xAI API.
Why this exists
The X/Twitter developer API has credit limits that can deplete independently of the xAI API. This skill uses the xAI API key (Grok models) which includes native X search as a server-side tool — no X developer API credits required.
When to use
- search — when you need to find what people are saying on X/Twitter, and the X developer API is unavailable or credits are depleted
- web_search — when you want Grok's web search as an alternative to the local searxng/Brave search
Prefer the x or x-research skills when X API credits are available — they return structured tweet data. Use this skill when those are unavailable or when you want Grok's synthesized take on X discourse.
Actions
search
Searches X/Twitter in real-time using Grok's x_search tool. Returns a synthesized answer with citations.
Input:
{
"query": "AI agents memory persistence",
"allowedXHandles": ["elonmusk"],
"excludedXHandles": ["spambot"],
"fromDate": "2026-07-01",
"toDate": "2026-07-23",
"model": "grok-4.5"
}
All parameters except query are optional. Date format: ISO 8601 (YYYY-MM-DD or full datetime).
web_search
Searches the web using Grok's web_search tool.
Input:
{
"query": "latest AI agent frameworks 2026",
"model": "grok-4.5"
}
What you get
- A synthesized text answer from Grok based on real X/web search results
- Citation URLs where available
- The search queries Grok used internally
What you don't get
- Raw tweet JSON or structured tweet objects (use
xorx-researchskills for that) - Posting or replying capability (that requires the X API OAuth credentials)
- Retweet/like counts as structured data
Gotchas
- Uses the xAI API key from
config/secrets.yamlunderxai.apiKey, orXAI_API_KEYenv var - Default model is
grok-4.5;grok-4.3also works - The xAI Responses API is the endpoint used (
/v1/responses), not chat completions - Grok synthesizes rather than returning raw search results — the output is an AI-generated summary with citations
allowed_x_handlesandexcluded_x_handleseach have a max of 20 handles (xAI API limit)- Grok decides how many results to return based on query scope — there is no result count parameter
- Rate limits follow the xAI API plan, not the X developer API plan
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.
- 11d ago First seen · 68 lines · 0 tokens per session scan A 16c0728e2322
xai-search is a skill published in the GitHub repository notforyou23/home23 (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 634 tokens. 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…