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 skills add flthibau/sample-OpenClaw-on-Azure-with-AI-Foundry --skill twitter-readergit clone --depth 1 https://github.com/flthibau/sample-OpenClaw-on-Azure-with-AI-FoundryWrote 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/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/twitter-reader)<a href="https://agentmods.dev/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/twitter-reader"><img src="https://agentmods.dev/badge/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/twitter-reader/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.
<a href="https://agentmods.dev/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/twitter-reader"><img src="https://agentmods.dev/badge/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/twitter-reader.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.00578 |
| Opus 5 | $0.00035 | $0.00289 |
| Sonnet 5 | $0.00014 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
twitter-reader 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 12d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twitter / X Reader
Read tweets, timelines, and user profiles from Twitter/X without API keys.
What it does
This skill lets you read Twitter/X content using two free, no-auth public endpoints:
- Twitter Syndication API — for user timelines (latest tweets)
- FxTwitter API — for individual tweet details and user profiles
Commands
Read a user's recent tweets
node skills/twitter-reader/run.js --user <handle> [--count N]
Example: node skills/twitter-reader/run.js --user OpenAI --count 5
Read a specific tweet
node skills/twitter-reader/run.js --tweet <tweet_id_or_url>
Example: node skills/twitter-reader/run.js --tweet https://x.com/OpenAI/status/1889753204340265039
Or: node skills/twitter-reader/run.js --tweet 1889753204340265039
Get a user profile
node skills/twitter-reader/run.js --profile <handle>
Example: node skills/twitter-reader/run.js --profile elonmusk
Search tweets
For search, use the web_search tool with site:x.com <query>.
Output formats
- Default: human-readable text with emojis
- JSON: add
--format jsonfor structured output
Instructions
When the user asks to read tweets, check a Twitter/X timeline, or look up a Twitter user:
- For timelines: run
node skills/twitter-reader/run.js --user <handle> --count <N> - For specific tweets (URL or ID): run
node skills/twitter-reader/run.js --tweet <id_or_url> - For user profiles: run
node skills/twitter-reader/run.js --profile <handle> - For tweet search: use
web_searchwith querysite:x.com <search terms>
Always present the results in a clean, readable format. Include engagement metrics (likes, retweets) and dates.
Limitations
- Timeline returns ~20 most recent tweets (Twitter syndication limit)
- No access to replies, DMs, or private accounts
- Rate limits may apply if called very frequently
- Search is delegated to web_search (Bing grounding)
No API key required
This skill uses public endpoints that don't require authentication.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 67 lines · 70 tokens per session scan A 08dc2fa7e80d
twitter-reader is a skill published in the GitHub repository flthibau/sample-OpenClaw-on-Azure-with-AI-Foundry (5 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 578 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…