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/community-managementnpx skills add nirholas/XActions --skill community-managementgit 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/community-management)<a href="https://agentmods.dev/skills/nirholas/xactions/community-management"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/community-management.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.00042 | $0.01091 |
| Opus 5 | $0.00021 | $0.00545 |
| Sonnet 5 | $0.00008 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
community-management 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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Management
Browser console scripts for managing X/Twitter Communities — leaving, joining, and interacting.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Leave ALL communities | src/leaveAllCommunities.js |
x.com/communities |
| Join communities by topic | src/joinCommunities.js |
x.com/i/communities/suggested |
Leave All Communities
File: src/leaveAllCommunities.js
Paste into DevTools on x.com/communities.
How It Works
The script navigates between pages to process each community:
- On communities list — Finds all community links, navigates to first unprocessed one
- On community page — Clicks "Joined" button → confirms Leave → marks as processed → navigates back
- On completion — Displays final count and exports results as JSON
Uses sessionStorage key xactions_left_communities (JSON array of community IDs) to survive page navigations. Re-running resumes where it stopped.
Controls
window.XActions.pause()— Pause executionwindow.XActions.resume()— Resumewindow.XActions.abort()— Stop and export progress
Reset Progress
sessionStorage.removeItem('xactions_left_communities')
Note: sessionStorage clears automatically when the browser tab closes.
Join Communities
File: src/joinCommunities.js
Navigate to community discovery pages and paste the script to auto-join communities matching your interests.
How It Works
- Scrapes visible community cards from the suggestions page
- Filters by keyword matching against community names and descriptions
- Clicks "Join" on matching communities with delays between actions
- Tracks joined communities to avoid duplicates
DOM Selectors
| Element | Selector | Notes |
|---|---|---|
| Community links | a[href^="/i/communities/"] |
Links to individual communities |
| Joined button | button[aria-label^="Joined"] |
Shows "Joined" status |
| Join button | [data-testid="TopicFollow"] |
Join community button |
| Community name | [data-testid="communityName"] |
Community title text |
| Confirmation dialog | [data-testid="confirmationSheetConfirm"] |
Leave confirmation |
| Back button | [data-testid="app-bar-back"] |
Navigate back |
| Communities nav | a[aria-label="Communities"] |
Main nav link |
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.
- 5d ago First seen · 125 lines · 42 tokens per session scan A 5cfc87b3bcca
community-management is a skill published in the GitHub repository nirholas/XActions (502 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 1,091 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…