twitter

A tool for searching and retrieving public content from Twitter/X, including user information, posts, replies, followers, communities, spaces, and trends.

In plain words
What is it for?
Use it to search users and posts, inspect replies and mentions, review followers or following lists, and check trends or communities.
Why use it?
It reduces the effort of gathering information from many accounts, conversations, and activity types on the platform.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/resciencelab/opc-skills/twitter
Any agent
npx skills add ReScienceLab/opc-skills --skill twitter
Clone the repo
git clone --depth 1 https://github.com/ReScienceLab/opc-skills

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00760
Opus 5 $0.00021 $0.00380
Sonnet 5 $0.00008 $0.00152
Haiku 4.5 $0.00004 $0.00076

Measured yesterday against content hash aee0659da20b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

twitter 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 yesterday.

The scan reads SKILL.md. This mod also ships 28 executable files (scripts/batch_get_users.py, scripts/check_relationship.py, scripts/credential.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/twitter/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Twitter/X Skill

Get user profiles, tweets, replies, followers/following, communities, spaces, and trends from Twitter/X via twitterapi.io.

Prerequisites

Set API key in ~/.zshrc:

export TWITTERAPI_API_KEY="your_api_key"

Quick Check:

cd <skill_directory>
python3 scripts/get_user_info.py elonmusk

Commands

All commands run from the skill directory.

User Endpoints

python3 scripts/get_user_info.py USERNAME
python3 scripts/get_user_about.py USERNAME
python3 scripts/batch_get_users.py USER_ID1,USER_ID2
python3 scripts/get_user_tweets.py USERNAME --limit 20
python3 scripts/get_user_mentions.py USERNAME --limit 20
python3 scripts/get_followers.py USERNAME --limit 100
python3 scripts/get_following.py USERNAME --limit 100
python3 scripts/get_verified_followers.py USERNAME --limit 20
python3 scripts/check_relationship.py USER1 USER2
python3 scripts/search_users.py "query" --limit 20

Tweet Endpoints

python3 scripts/get_tweet.py TWEET_ID [TWEET_ID2...]
python3 scripts/search_tweets.py "query" --type Latest --limit 20
python3 scripts/get_tweet_replies.py TWEET_ID --limit 20
python3 scripts/get_tweet_quotes.py TWEET_ID --limit 20
python3 scripts/get_tweet_retweeters.py TWEET_ID --limit 50
python3 scripts/get_tweet_thread.py TWEET_ID
python3 scripts/get_article.py TWEET_ID

List Endpoints

python3 scripts/get_list_followers.py LIST_ID --limit 20
python3 scripts/get_list_members.py LIST_ID --limit 20

Community Endpoints

python3 scripts/get_community.py COMMUNITY_ID
python3 scripts/get_community_members.py COMMUNITY_ID --limit 20
python3 scripts/get_community_moderators.py COMMUNITY_ID
python3 scripts/get_community_tweets.py COMMUNITY_ID --limit 20
python3 scripts/search_community_tweets.py "query" --limit 20

Other Endpoints

python3 scripts/get_space.py SPACE_ID
python3 scripts/get_trends.py --woeid 1  # Worldwide

Search Query Syntax

# Basic search
python3 scripts/search_tweets.py "AI agent"

# From specific user
python3 scripts/search_tweets.py "from:elonmusk"

# Date range
python3 scripts/search_tweets.py "AI since:2024-01-01 until:2024-12-31"

# Exclude retweets
python3 scripts/search_tweets.py "AI -filter:retweets"

# With media
python3 scripts/search_tweets.py "AI filter:media"

# Minimum engagement
python3 scripts/search_tweets.py "AI min_faves:1000"

Read the full file on GitHub · 100 lines

Changes

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.

  1. yesterday First seen · 100 lines · 42 tokens per session scan A aee0659da20b

Subscribe to this mod's changes

twitter is a skill published in the GitHub repository ReScienceLab/opc-skills (1,710 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 760 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

context-okf-llm-ingest

Use when extracting a codebase's implementation decisions into Metatron with an LLM/agent instead of metatron ingest — authoring candidate decisions as Open Knowledge Format (OKF) markdown files locally for review.

kerbelp/metatron · 53 tokens

context-okf-promote-candidates

Use when promoting reviewed Metatron candidate decisions to canonical in a git/CI flow — moving Open Knowledge Format (OKF) files from candidate/ to decisions/. The agent performs only human-named moves; it never decides what to promote.

kerbelp/metatron · 56 tokens

live-audit

Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…

Grinv/steam-games-mcp · 83 tokens

live-audit

Repo-specific playbook, for any agent/model working on this repo (not tied to a particular harness — see AGENTS.md's own framing). Use it when asked to test/audit/smoke-test the published tmdb-mcp package, hunt for bugs or edge cases, or repeat "the same kind of testing as before.".

Grinv/tmdb-mcp · 0 tokens

prompt-check

Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.

Grinv/steam-games-mcp · 54 tokens

prompt-check

Live-test every MCP Prompt in src/prompts.ts through the real MCP protocol (not a static read) across every argument combination, including every enum value. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.

Grinv/tmdb-mcp · 58 tokens