A research tool for collecting and analyzing posts from X, formerly known as Twitter. It uses Apify, a service that runs web-scraping programs, to study topics, communities, trends, accounts, and engagement.

Use it for topic research, trend discovery, community analysis, account analysis, feed scanning, and engagement analysis.

It removes the need to manually gather many posts when you need to understand what people are discussing or responding to.

x-insights — Skill for Claude Code by MSApps-Mobile/claude-plugins

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.

Any agent

npx skills add MSApps-Mobile/claude-plugins --skill x-insights

Clone the repo

git clone --depth 1 https://github.com/MSApps-Mobile/claude-plugins

Made for: Claude Code.

Or install x-content-intelligence, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/x-insights/github.svg)](https://agentmods.dev/skills/msapps-mobile/claude-plugins/x-insights)

Your own site

<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/x-insights"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/x-insights/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/x-insights"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/x-insights.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,153 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00136	$0.01153
Opus 5.5	$0.00054	$0.00461
Sonnet 5.5	$0.00027	$0.00231
Haiku 4.5	$0.00014	$0.00115

Measured 1mo ago against content hash 3f6c0f47f740, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

x-insights 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 1mo 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.

plugins/x-content-intelligence/skills/x-insights/SKILL.md · 130 lines

How it starts

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

X Insights — Scrape & Analyze X (Twitter) Content

Scrape X (Twitter) using Apify and analyze the results to extract actionable insights about communities, trends, engagement patterns, and content performance.

Requirements

Apify MCP must be connected (the apify MCP with call-actor and get-actor-output tools)
The recommended Apify Actor is apidojo/tweet-scraper (Tweet Scraper V2)

Workflow

Step 1: Clarify the Scraping Goal

Before scraping, determine what the user wants to learn. Common use cases:

Community analysis: Understand what a specific X community talks about, their tone, popular topics
Trend discovery: Find what's trending around specific keywords, hashtags, or topics
Account analysis: Analyze a specific account's content, engagement, and posting patterns
Topic research: Gather posts about a specific subject to understand the conversation
Feed scanning: Broad scan of a topic area for general intelligence and interesting content
Engagement analysis: Understand what types of posts get the most engagement in a niche

Ask the user to specify: keywords/hashtags to search, specific accounts to analyze, time range, and how many posts to gather.

Step 2: Scrape X Using Apify

Use the apidojo/tweet-scraper Actor with appropriate input configuration.

For keyword/hashtag search:

{
  "searchTerms": ["keyword1", "#hashtag1"],
  "maxItems": 100,
  "sort": "Top"
}

For profile scraping:

{
  "twitterHandles": ["handle1", "handle2"],
  "maxItems": 50
}

For URL-based scraping:

{
  "startUrls": ["https://x.com/..."],
  "maxItems": 50
}

Run the Actor using call-actor with Actor name apidojo/tweet-scraper, then retrieve results with get-actor-output.

Step 3: Analyze the Results

Once data is retrieved, perform the analysis the user requested. Structure the analysis around these dimensions as relevant:

Content Analysis:

What topics/themes appear most frequently?
What questions are people asking?
What problems or pain points are mentioned?
What solutions or tools are being discussed?

Read the full file on GitHub · 130 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.

1mo ago First seen · 130 lines · 136 tokens per session scan A 3f6c0f47f740

Subscribe to this mod's changes

x-insights is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 1,153 once invoked, about $0.0005 per session on Opus 5.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-09-13.

Analytics and metrics Claude Code Research agent-safety ai-agents ai-governance claude claude-plugins

live-preview

Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.

SethGammon/Citadel · 40 tokens

wiki

Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.

SethGammon/Citadel · 56 tokens

x-insights