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/nirholas/xactions/discovery-explorenpx skills add nirholas/XActions --skill discovery-exploregit clone --depth 1 https://github.com/nirholas/XActionsWhat 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.00059 | $0.00828 |
| Opus 5 | $0.00030 | $0.00414 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
discovery-explore 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery & Explore
Browser console scripts and MCP tools for exploring trends, searching content, and discovering accounts on X/Twitter.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Monitor trending topics | src/trendingTopicMonitor.js |
x.com/explore/tabs/trending |
| Search tweets | scripts/scrapeSearch.js |
Search results page |
| Scrape hashtag | scripts/scrapeHashtag.js |
x.com/hashtag/TAG |
| Find viral tweets | src/viralTweetDetector.js |
Any profile |
| Keyword monitoring | src/keywordMonitor.js |
Any page |
| Scrape explore page | src/exploreScraper.js |
x.com/explore |
MCP Tools
| Tool | Description |
|---|---|
x_get_trends |
Current trending topics |
x_get_explore |
Explore page content |
x_search_tweets |
Full-text tweet search |
Trending Topic Monitor
File: src/trendingTopicMonitor.js
Real-time trending topic scraper with niche classification.
Controls
XActions.scan()-- Scrape current trendsXActions.track()-- Log trend snapshot with timestampXActions.history()-- Show all tracked snapshotsXActions.forNiche(keyword)-- Filter trends by niche keywordXActions.export()-- Download trend data as JSON
Features
- Categorizes trends by niche (tech, politics, entertainment, sports, crypto, etc.)
- Tracks trend velocity (rising/falling)
- Identifies trending hashtags vs organic trends
- Alerts on niche-relevant trends
Keyword Monitor
File: src/keywordMonitor.js
Monitors X for mentions of specific keywords with sentiment classification.
Controls
XActions.setKeywords(['keyword1', 'keyword2'])-- Configure keywordsXActions.scan()-- Run one search cycleXActions.autoScan(intervalMs)-- Continuous monitoringXActions.stop()-- Stop auto-scanningXActions.report()-- Show summary with sentiment breakdownXActions.export()-- Download results as JSON
Strategy Guide
Trend-jacking workflow
- Run
src/trendingTopicMonitor.js->XActions.forNiche('your_niche') - Identify relevant trends with momentum
- Craft timely content using
src/threadComposer.jsorsrc/contentRepurposer.js - Post within the first 2 hours of trend emergence for maximum visibility
- Track performance with
src/tweetPerformance.js
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.
- 3d ago First seen · 91 lines · 59 tokens per session scan A cf260c1ea932
discovery-explore is a skill published in the GitHub repository nirholas/XActions (496 stars, last pushed 5d ago), licensed Apache-2.0. It adds 59 tokens to every session and 828 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-30.
Other skills, from other repositories
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
browser-test
Validate a feature works by driving a real browser with Playwright MCP. No test files — just interactive verification.
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-pair
Collaborative headed browser session for UI work. Launch Playwright Chromium visible to the user, handle auth, then interactively drive the browser while the user watches and gives real-time visual feedback. Edit code and refresh to verify fixes live. Use when the user says 'browser pair', 'paired browser', 'let's…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…