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 skills/siddsachar/row-bot/x_guidenpx skills add siddsachar/row-bot --skill x_guidegit clone --depth 1 https://github.com/siddsachar/row-botWrote 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/siddsachar/row-bot/x_guide)<a href="https://agentmods.dev/skills/siddsachar/row-bot/x_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/x_guide.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.00025 | $0.00516 |
| Opus 5 | $0.00013 | $0.00258 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
x_guide 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 4d 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.
What it actually says
X (TWITTER) TOOL GUIDANCE:
- You have X tools for reading, posting, and engaging on X (Twitter).
- Three composite tools: x_read (search/read), x_post (post/reply/quote/delete), x_engage (like/unlike/repost/bookmark).
SEARCH QUERY RULES (x_read with action='search'):
- The query parameter accepts PLAIN KEYWORDS and official X API v2 operators ONLY.
- SUPPORTED operators: from:username, to:username, @username, #hashtag, is:retweet, is:reply, is:quote, has:links, has:media, has:images, lang:en, -keyword (exclude), "exact phrase" (quoted).
- UNSUPPORTED operators (will cause API errors): since:, until:, within_time:, near:, geocode:. These are Twitter web UI operators and do NOT work with the API.
- For TIME FILTERING, use the start_time and end_time parameters instead. These accept ISO 8601 (e.g. '2026-04-14T00:00:00Z') or relative formats like '1h', '24h', '7d', '2w'.
- The search endpoint only covers the last 7 days of tweets.
POSTING RULES:
- All post operations (post, reply, quote, delete) require approval.
- Tweets have a 280-character limit for text content.
- When replying, always include the tweet_id of the tweet being replied to.
- When quoting, include both text (your commentary) and tweet_id (the tweet being quoted).
ENGAGEMENT PATTERNS:
- Like, repost, and bookmark operations are reversible (unlike, unrepost, unbookmark).
- Always confirm with the user before engaging with tweets on their behalf.
BACKGROUND TASK EXAMPLES:
- For monitoring tasks, use search with start_time='1h' to check recent tweets since the last poll. Use persistent_thread to track what was already seen.
- For engagement tasks, combine x_read search with x_engage actions.
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.
- 4d ago First seen · 48 lines · 25 tokens per session scan A 4718d097bc77
x_guide is a skill published in the GitHub repository siddsachar/row-bot (1,480 stars, last pushed 6d ago), licensed Apache-2.0. It adds 25 tokens to every session and 516 once invoked, about $0.0001 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.
Other skills, from other repositories
twitter-agent
Build and run a Twitter/X agent with a distinct personality and automated workflows.
X
Operate on X/Twitter through the canonical Home23 X skill. Uses the logged-in bird browser session by default; official API access is explicit opt-in.
social-x-post-card
拟真 X 推文卡片 + 互动数据 (likes/reposts/views), 适配视频叠加或图卡分享.
x-api
Read X/Twitter via API, post tweets with OAuth 1.0a, and draft X Articles through shitrat x. Check mentions, search, and ingest posts. Use app bearer tokens for read-only fetches. Use OAuth 1.0a user context for tweets. Use shitrat x for Articles.
social-x-post-card
Realistic X post card with engagement metrics (likes, reposts, views), suited to video overlays or shareable image cards.
social-x-post-card
Realistic X post card with engagement metrics (likes, reposts, views), suited to video overlays or shareable image cards.