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 answer for follow-up, and returns it without content filtering or automatic browser verification. For ordinary web research, use when Grok is requested, native search is insufficient, or social evidence matters. Do not use for local-file work or summarizing complete supplied material.
npx skills add sudoHG/codex-grok-search --skill codex-grok-search --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Codex + Grok Search Use this Skill as a thin bridge to Grok. Prioritize delivering Grok's answer. ## Run 1. Resolve the absolute directory containing this `SKILL.md` as `<skill-dir>`. 2. Choose `x`, `reddit`, `web`, or `auto` as a search hint. The hint is not an exclusion rule. 3. Use `quick` unless the user explicitly requests deep research or cross-checking. 4. Convert an explicit relative window such as “last 7 days” to `--since 7d`. 5. Run: ```sh python3 "<skill-dir>/scripts/run_search.py" run \ --platform auto \ --depth quick \ --since 7d \ "<complete user request>" ``` 6. Read the JSON status from stdout, then read the complete Grok answer at `result_path`. 7. Answer in the user's language. Do not open returned links, invoke a browser, or independently cross-check unless the user asks. The bridge always requests `grok-4.5`. It gives Grok access to X Search and public-web search/fetch so Grok can use whatever public sources help answer the request. ## Preserve Grok's answer - Do not reject, delete, rewrite, or filter a result because it includes another platform, an `http` URL, an unverifiable date, a missing field, or free-form Markdown. - If Grok expresses uncertainty, pre
- Run
- Preserve Grok's answer
- Continue a prior run
- Failures
python3 "<skill-dir>/scripts/run_search.py" run \ python3 "<skill-dir>/scripts/run_search.py" list python3 "<skill-dir>/scripts/run_search.py" show <run-id>
What does the codex-grok-search skill do?
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 answer for follow-up, and returns it without content filtering or automatic browser verification. For ordinary web research, use when Grok is requested, native search is insufficient, or social evidence matters. Do not use for local-file work or summarizing complete supplied material.
How do I install it?
Run `npx skills add sudoHG/codex-grok-search --skill codex-grok-search --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sudoHG/codex-grok-search, a repository with 51 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.