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 follower-monitoringgit 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/follower-monitoring)<a href="https://agentmods.dev/skills/nirholas/xactions/follower-monitoring"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/follower-monitoring/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/follower-monitoring"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/follower-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.00985 |
| Opus 5 | $0.00034 | $0.00492 |
| Sonnet 5 | $0.00014 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
follower-monitoring 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follower Monitoring
Browser console scripts for tracking follower changes on X/Twitter. All scripts use localStorage for persistent snapshot comparison.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Detect who unfollowed you | src/detectUnfollowers.js |
x.com/USERNAME/followers |
| Monitor any public account | src/monitorAccount.js |
x.com/TARGET/followers |
| Continuous monitoring + alerts | src/continuousMonitor.js |
x.com/USERNAME/followers |
| New follower tracking + welcome | src/newFollowersAlert.js |
x.com/USERNAME/followers |
| Follower growth over time | src/followerGrowthTracker.js |
x.com/USERNAME/followers |
| Follower demographics | src/audienceDemographics.js |
x.com/USERNAME/followers |
| Audit follower quality | src/auditFollowers.js |
x.com/USERNAME/followers |
| Follow ratio management | src/followRatioManager.js |
x.com/USERNAME |
How They Work
All scripts use the same snapshot-compare pattern:
- First run: Scrapes visible users by scrolling, saves snapshot to localStorage
- Subsequent runs: Scrapes current list, compares against saved snapshot, reports additions/removals
detectUnfollowers.js
Compares follower snapshots. Auto-downloads unfollowers as .txt file. Simple two-run workflow: paste once to baseline, paste again later to detect changes.
monitorAccount.js
Works on ANY public account (not just yours). Tracks both followers and following list changes. Downloads removed accounts list.
continuousMonitor.js
Long-running script with auto-refresh on interval (default: 5 minutes). Sends browser Notification API alerts and plays Web Audio API sounds on changes. Tab must stay open.
newFollowersAlert.js
Tracks new followers with display names. Generates welcome message templates. Also reports unfollowers as secondary output.
followerGrowthTracker.js
Records follower count snapshots over time with timestamps. Calculates daily/weekly/monthly growth rates. Projects future milestones. Visual growth chart in console.
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 · 94 lines · 69 tokens per session scan A b402c470d3c1
follower-monitoring is a skill published in the GitHub repository nirholas/XActions (518 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 985 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
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.
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…
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
browser-automation-studio
Reference for using Browser Automation Studio (BAS) to execute browser workflows, validate UI behavior, and debug automation failures.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.