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 agentmods add instructions/ilevk/x-search-plugin/agents-mdgit clone --depth 1 https://github.com/Ilevk/x-search-pluginWrote 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/instructions/ilevk/x-search-plugin/agents-md)<a href="https://agentmods.dev/instructions/ilevk/x-search-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/ilevk/x-search-plugin/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
x-search-plugin AGENTS.md 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Guide
Project Goal
This repository provides an MCP plugin for read-only X/Twitter research through
xAI's Responses API x_search tool. Codex and Claude Code are the first
supported client surfaces.
The primary authentication path is xAI OAuth for entitled X Premium, Premium+,
and SuperGrok accounts. XAI_API_KEY remains a fallback path. Do not redesign
the project around browser scraping or X API v2 unless Logan explicitly changes
the goal.
Boundaries
- Must remain read-only: no posting, liking, following, DM access, deletes, or account mutation.
- Do not read browser cookies, X app storage, or Hermes credential files.
- Do not print, log, commit, or ask the user to paste access tokens, refresh
tokens, API keys, or credential file contents. OAuth authorization codes may
be pasted only into the local
uv run --quiet --locked python scripts/x_search_auth.py login --manual-pasteterminal prompt, never into chat or docs. Prefer full callback URLs or?code=...&state=...fragments over bare authorization codes. - Treat
XAI_BASE_URLas a credential sink. Do not use real OAuth/API-key credentials with untrusted override endpoints. - Non-x.ai
XAI_BASE_URLwith env fallback credentials requiresX_SEARCH_ALLOW_UNTRUSTED_BASE_URL=1and is for local tests only. - OAuth state belongs under
~/.x-search-plugin/auth.jsonby default, or underX_SEARCH_PLUGIN_HOMEwhen explicitly set. - Legacy
~/.x-search-codex/auth.jsonandX_SEARCH_CODEX_HOMEare supported only for users who authenticated before the project rename. - Keep the implementation dependency-light. The current runtime uses Python standard library only.
Implementation Conventions
- Keep MCP protocol behavior in
scripts/x_search_mcp.py. - Keep OAuth login, refresh, status, and credential resolution in
scripts/xai_oauth.py. - Keep human-facing auth commands in
scripts/x_search_auth.py. - Preserve API-key fallback behavior when changing OAuth logic.
- Prefer explicit, structured JSON tool results. Missing credentials and upstream failures should return clear tool errors rather than stack traces.
- Validate external inputs at the tool boundary. Date ranges should be strict; handle filters should at minimum be normalized, bounded, and kept mutually exclusive where required.
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.
- 2d ago First seen · 104 lines · 1,062 tokens per session scan A e0aae55d49fa
x-search-plugin AGENTS.md is an instructions file published in the GitHub repository Ilevk/x-search-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.