Agent Reach
Panniantong/Agent-Reach
Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.
Rules for using the x_search tool to search X (Twitter) through a connected xAI account: date-bound queries, trusted handles, search operators and split searches.
Install X Search via xAI
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent x-search --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .claude/skills/x-search && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .claude/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent x-search --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .agents/skills/x-search && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .agents/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent x-search --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .cursor/skills/x-search && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .cursor/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/code-yeongyu/oh-my-openagent.git --path packages/omo-senpi/src/components/x-search/skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent x-search --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .gemini/skills/x-search && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .gemini/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install code-yeongyu/oh-my-openagent x-searchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .github/skills/x-search && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .github/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill x-search -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install code-yeongyu/oh-my-openagent x-search --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/omo-senpi/src/components/x-search/skill .opencode/skills/x-search && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "x-search" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-senpi/src/components/x-search/skill into .opencode/skills/x-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "x-search", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
x-search- GitHub stars
- 70k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 695 words
- Files
- 1
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Rules for using the x_search tool to search X (Twitter) through a connected xAI account: date-bound queries, trusted handles, search operators and split searches.
- Works in 2 steps: Run tool_search "X posts". If x_search… → If nothing matches, xAI isn't connected.…
- Checking what people on X are saying about a launch or earnings report
- SKILL.md covers Which tool, The 4 rules, Operator cheat sheet and Split-search recipe, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This applies only when an xAI credential is connected. The agent looks for x_search through tool_search; if it does not appear, it says the tool is unavailable and falls back to web_search rather than guessing at posts from memory. The tool is a single round trip to xAI's server-side X search, so the agent's job is to shape the query and its parameters well.
Four rules guide each call. Time-sensitive queries get a from_date of yesterday, widened to seven days if results are thin. Accounts the user trusts go in allowed_x_handles, as bare handles with a maximum of 20, and cannot be combined with excluded_x_handles. Queries use recency wording plus X operators such as since:, until:, from:, filter:links, -filter:replies and lang:. One broad query is replaced by two to three narrower searches, split by account and by keyword, with a thread fetch when one post's replies matter. Results are cross-checked against web_search.
When your agent uses it
- Checking what people on X are saying about a launch or earnings report
- Searching posts from a specific list of trusted accounts
- Looking up recent posts by keyword with date and language filters
- Reading the replies under a single post
Example prompts
- “Search X for reactions to yesterday's earnings call, only from the accounts I listed.”
- “Find what people on X have posted this week about the new React release, in English only.”
- “Fetch the reply thread under the latest post from @vercel and summarize the main objections.”
Requirements
- A connected xAI account that exposes the x_search tool
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Run tool_search "X posts". If x_search shows up, it's callable on the
- If nothing matches, xAI isn't connected. Say so plainly ("x_search is
What it can do on your machine
Read from SKILL.md and the folder at commit ab81169. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
X Search via xAI loads about 1.4k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 695 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 695 words (~1,367 tokens).
“This skill only matters when an xAI account is connected. The x_search tool is registered at load time if a credential exists, and it is hidden behind tool_search until you activate it. Everything below assumes you've read the current date…”
- name
- x-search
Files
Just SKILL.md in packages/omo-senpi/src/components/x-search/skill of code-yeongyu/oh-my-openagent.
Open the folder on GitHubat commit ab81169
Compare with similar skills
X Search via xAI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| X Search via xAI this skillcode-yeongyu/oh-my-openagent | 70k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Agent ReachPanniantong/Agent-Reach | 93k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Modsearchliustack/modsearch | 603 | 1 repos | ~2.6k | Automated safety check: Notes | MIT | |
| Agent ReachEdisonChenAI/agent-reach | 106 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| What Happenedkunchenguid/whathappened | 230 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Content Harvestercharlie-chann/ai-agent-langgraph-main | 114 | — | ~233 | Automated safety check: Pass | None |
Similar skills
Modsearch
liustack/modsearch
Plug-in web search, X (Twitter) search, and page fetch for models without native web access.
Agent Reach
EdisonChenAI/agent-reach
Use the internet: search, read, and interact with 13+ platforms including Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu (小红书), Douyin (抖音), WeChat Articles (微信公众号), LinkedIn, Boss直聘…
What Happened
kunchenguid/whathappened
Briefs you on what just happened around a named topic and maps public opinion on X, using the host's native X search tools only.
Content Harvester
charlie-chann/ai-agent-langgraph-main
多源内容采集专家。能从网页、RSS、Tavily搜索、Twitter抓取内容。适用于：信息收集、竞品监控、行业动态追踪。
Copy Research
VKirill/claude-lane-stack
Dispatch copy-lead helpers: Tavily, Codex luna/terra, grok/X, OpenCode DeepSeek, Cursor Grok 4.6 medium-fast.
More from code-yeongyu/oh-my-openagent
All 45 skills in this repoBrowser Control with Omowright
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
LSP Setup
code-yeongyu/oh-my-openagent
Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
Related
Works with
Categories
Questions about X Search via xAI
What does X Search via xAI do?
Rules for using the x_search tool to search X (Twitter) through a connected xAI account: date-bound queries, trusted handles, search operators and split searches. This applies only when an xAI credential is connected. The agent looks for x_search through tool_search; if it does not appear, it says the tool is unavailable and falls back to web_search rather than guessing at posts from memory.
When should I use X Search via xAI?
X Search via xAI fits situations like: checking what people on X are saying about a launch or earnings report; searching posts from a specific list of trusted accounts; looking up recent posts by keyword with date and language filters; reading the replies under a single post.
How do I install X Search via xAI in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill x-search -a claude-code`. Or copy the skill folder (packages/omo-senpi/src/components/x-search/skill in code-yeongyu/oh-my-openagent) into .claude/skills/x-search in your project. Claude Code loads it when a task matches its description.
How do I install X Search via xAI in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill x-search -a codex`. Or copy the skill folder (packages/omo-senpi/src/components/x-search/skill in code-yeongyu/oh-my-openagent) into .agents/skills/x-search in your project. Codex loads it when a task matches its description.
Can I use X Search via xAI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill x-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/x-search, .gemini/skills/x-search, .github/skills/x-search and .opencode/skills/x-search in your project.
What does X Search via xAI need to run?
SKILL.md names no scripts, command-line tools or credentials: X Search via xAI is instructions for the agent only. Our summary lists: A connected xAI account that exposes the x_search tool.
Does X Search via xAI access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is X Search via xAI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does X Search via xAI use?
X Search via xAI has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does X Search via xAI use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to X Search via xAI?
Skills that share tags, products or a category with X Search via xAI: Agent Reach (Panniantong/Agent-Reach, 93k stars), Modsearch (liustack/modsearch, 603 stars), Agent Reach (EdisonChenAI/agent-reach, 106 stars) and What Happened (kunchenguid/whathappened, 230 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains X Search via xAI?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,882 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 8, 2026.
Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.