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/aiyo28/xee-mcp/claude-mdgit clone --depth 1 https://github.com/Aiyo28/Xee-mcpWrote 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/aiyo28/xee-mcp/claude-md)<a href="https://agentmods.dev/instructions/aiyo28/xee-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/aiyo28/xee-mcp/claude-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.1 | $0.00690 | $0.00690 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
Xee-mcp CLAUDE.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 5d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xee-mcp — Agent Session Protocol
For Claude Code / Claude Desktop sessions working on this repo. Skinny by design.
Project shape
- What: MCP server for X (Twitter) — search + read only. Naming: X + See = Xee.
- Stack: Python 3.11+,
mcpSDK,twikitfor cookie-based scrape,uvfor deps. - Out of scope: posting, DMs, likes, retweets. If asked to add posting, push back — that's a separate repo (different threat model, different audit surface).
- Tag:
[OSS]per~/.claude/CLAUDE-current.mdPath B. Donation-only (paypal.me/aiyo28). No paid tiers ever.
Critical gotchas
- Read-only is law. Tools must never mutate X state. If a future contributor adds posting, reject the PR or move it to a separate repo.
- Cookie file path is via
XEE_MCP_COOKIESenv var. Never hardcode. Never log cookie contents. - twikit auth fragility. X may rotate session formats. If
searchoruser_tweetsstart returning empty, first check cookie validity, not code. - Single-account v0.1. Multi-account pool is v0.3 — only if reliable bot-detection forces it. Don't pre-build.
- Tool surface is two functions. Resist scope creep. New tools require a roadmap entry first.
- SEO/AEO discipline. README H1 and first paragraph are LLM-snippet targets. Don't change them without checking they still answer "What is Xee-mcp?" in <50 words.
- Bilingual EN-only v1. X audience is global, RU layer adds maintenance with no clear payoff. Invalidate only if RU/CIS audience signal becomes dominant.
- Name discipline. Repo + Python module + PyPI distro + CLI + server name + env vars all renamed from
mcp-xee→Xee-mcp(2026-05-17, vault [D]#4). Don't reintroduce the old name except in historical/changelog context.
Session opening checklist
- Read
README.md(~50 lines) andROADMAP.md(~30 lines) — the public surface contract. - If working on tools: read
src/xee_mcp/tools.pyandsrc/xee_mcp/client.pyfirst. - If working on auth: read
docs/cookies.md(when it exists). - Cross-project context lives in vault:
~/Documents/Developer/knowledge-os/Projects/Xee-mcp/_context.md.
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.
- 5d ago First seen · 37 lines · 690 tokens per session scan A 9d33fd39fef0
Xee-mcp CLAUDE.md is an instructions file published in the GitHub repository Aiyo28/Xee-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 690 tokens to every session, about $0.0034 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
markitdown-mcp AGENTS.md
Instructions for trsdn/markitdown-mcp, covering ai agents integration guide, 🤖 quick reference for ai agents, primary use cases, available tools and 🛠️ tool usage guide.
che-word-mcp CLAUDE.md
Claude Code instructions for PsychQuant/che-word-mcp, covering che-word-mcp 開發指引, 專案結構, 重要路徑規則, binary 安裝位置 and mcpb 打包檔位置.
tmdb-mcp AGENTS.md
Instructions for Grinv/tmdb-mcp, covering agents.md, project shape, commands, conventions and testing the live/published server.
steam-games-mcp AGENTS.md
Instructions for Grinv/steam-games-mcp, covering agents.md, project shape, commands, conventions and testing the live/published server.
FusionAL CLAUDE.md
Claude Code instructions for JRM-FusionAL/FusionAL, covering claude.md — fusional, session init — run this first, recall protocol (mandatory, visible), auto-log protocol (mandatory, ambient) and critical failure modes (already logged — do not repeat).
mal-mcp AGENTS.md
Instructions for Grinv/mal-mcp, covering agents.md, project shape, commands, conventions and testing the live/published server.