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 nirholas/XActions --skill xactions-cligit clone --depth 1 https://github.com/nirholas/XActionsWrote 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/nirholas/xactions/xactions-cli)<a href="https://agentmods.dev/skills/nirholas/xactions/xactions-cli"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/xactions-cli/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/nirholas/xactions/xactions-cli"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/xactions-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 101 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00064 | $0.00829 |
| Opus 5.5 | $0.00026 | $0.00332 |
| Sonnet 5.5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
xactions-cli 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XActions CLI
Entry point: src/cli/index.js. Config stored at ~/.xactions/config.json.
Installation
npm install -g xactions
Authentication
xactions login # Interactive prompt for auth_token cookie
xactions logout # Removes saved cookie
xactions info # Show current auth status and config
Get your auth_token: DevTools (F12) -> Application -> Cookies -> x.com -> copy auth_token value.
Scraping Commands
xactions profile <username>
xactions followers <username> [-l <limit>] [-o json|csv]
xactions following <username> [-l <limit>] [-o json|csv]
xactions non-followers <username>
xactions tweets <username> [-l <limit>] [-o json|csv]
xactions search "<query>" [-l <limit>] [-o json|csv]
xactions hashtag <tag> [-l <limit>] [-o json|csv]
xactions thread <url>
xactions media <username> [-l <limit>]
MCP Server Commands
xactions mcp-config # Generate config for Claude Desktop
xactions mcp-config --client cursor # Generate for Cursor
xactions mcp-config --client windsurf # Generate for Windsurf
xactions mcp-config --client vscode # Generate for VS Code
xactions mcp-config --write # Write config directly to file
The mcp-config command auto-detects your OS and generates the correct config file path.
Output Flags
| Flag | Description |
|---|---|
-l, --limit <n> |
Maximum items to scrape |
-o, --output <format> |
json or csv — saves to {username}_{command}.{ext} |
Default output is pretty-printed to terminal with colored formatting.
Programmatic API
The CLI wraps the same scraper API available as a library:
import { createBrowser, createPage, loginWithCookie,
scrapeProfile, scrapeFollowers, scrapeFollowing, scrapeTweets,
searchTweets, scrapeHashtag, scrapeThread, scrapeMedia,
exportToJSON, exportToCSV } from 'xactions';
Examples
# Scrape a profile
xactions profile elonmusk
# Export followers as CSV
xactions followers nichxbt -l 200 -o csv
# Search tweets and save as JSON
xactions search "AI agents" -l 50 -o json
# Unroll a thread
xactions thread https://x.com/nichxbt/status/1234567890
# Generate Claude Desktop MCP config
xactions mcp-config --write
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 · 109 lines · 64 tokens per session scan A 1ea2465a077e
xactions-cli is a skill published in the GitHub repository nirholas/XActions (594 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 829 once invoked, about $0.0003 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-03.
Other skills, from other repositories
drive-the-ui
Drive the page the user has open through live UI actions. List the actions a page accepts, call them with typed payloads, and read the live state including unsaved edits. Use when the user is looking at a page you can operate, such as the evaluations workbench, and a change should happen in front of them rather than…
browser-test
Check that a feature works by walking its scenarios in a real browser and writing a pass/fail report with evidence. A recipe over haven browser: no test files, no browser commands of its own. Use when someone says 'browser test', 'verify this in the browser', 'walk the scenarios', 'check the feature live', or hands…
haven-auth
Sign in to this worktree's stack as admin or a seeded login with haven browser login --as, which writes a Playwright storage-state file and never prints the password. Use when someone says 'haven auth', 'haven browser login --as', 'sign in as admin', 'log in as a seeded user', 'storage state', 'a signed-in session for…
haven-orb
Read what a person sent from the haven orb on the app page: haven orb feedback notes with selector, viewport, console and requests, and haven orb console|network. Use when someone says 'haven feedback', 'haven page console', 'haven orb feedback', 'the haven orb', 'read the notes I left', 'resolve the feedback', 'wait…
browser-telemetry-and-errors
What the small browser support packages are for and when feature code uses them: packages/react-rum (browser traces, error spans, navigation spans; the host starts it, features do not), packages/error-views (HandledErrorState, HandledErrorAlert, FormServerError, AggregateReadOnlyGate, resolveErrorCopy), the error…
browser-pair
Iterate on UI with a person watching and giving live visual feedback. Pointer skill: the person uses their own tab on the stack and the haven orb; you read their notes and check fixes with haven browser. Use when the user says 'browser pair', 'paired browser', 'let's look at this together', 'open chromium', or wants…