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/saved-searchesnpx skills add nirholas/XActions --skill saved-searchesgit 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/saved-searches)<a href="https://agentmods.dev/skills/nirholas/xactions/saved-searches"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/saved-searches.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.1 | $0.00049 | $0.00500 |
| Opus 5 | $0.00024 | $0.00250 |
| Sonnet 5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
saved-searches 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 6d 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
Saved Searches
Browser console scripts for managing saved searches on X/Twitter.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Save a search query | src/saveSearch.js |
x.com/search?q=... (search results page) |
| List / delete / run saved searches | src/savedSearchManager.js |
x.com |
Quick Start
Save a search
- Search for something on X:
x.com/search?q=your+query - Open DevTools (F12) → Console
- Paste
src/saveSearch.js→ Enter
Manage saved searches
- Go to
x.com - Open DevTools (F12) → Console
- Paste
src/savedSearchManager.js→ Enter
Available Functions (savedSearchManager.js)
XActions.list() // List all saved searches
XActions.run('query') // Run a saved search (navigates to results)
XActions.delete('query') // Delete a saved search by name
XActions.export() // Export all saved searches as JSON
Configuration
const CONFIG = {
maxTweets: 100, // Max tweets to collect when running a search
scrollDelay: 2000, // ms between scroll actions
actionDelay: 1500, // ms between UI actions
maxScrollAttempts: 25, // Max scroll rounds before stopping
};
Notes
- X limits saved searches to 25 per account
- Saved searches are stored in your X account (not just browser storage)
savedSearchManager.jscan also scrape trending topics for discovery
Related Skills
- discovery-explore — Browse trending topics and explore without saved searches
- analytics-insights — Analyze search results for hashtags and keywords
- twitter-scraping — Scrape full search result data
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.
- 6d ago First seen · 66 lines · 49 tokens per session scan A ad14b2c70878
saved-searches is a skill published in the GitHub repository nirholas/XActions (509 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 500 once invoked, about $0.0002 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
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.
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
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…