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 notifications-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/notifications-management)<a href="https://agentmods.dev/skills/nirholas/xactions/notifications-management"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/notifications-management/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/notifications-management"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/notifications-management.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.00043 | $0.00644 |
| Opus 5.5 | $0.00017 | $0.00258 |
| Sonnet 5.5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
notifications-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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notifications Management
Browser console script for managing and filtering X/Twitter notifications.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Filter and manage notifications | src/notificationManager.js |
x.com/notifications |
| Scrape notification data | scripts/scrapeNotifications.js |
x.com/notifications |
| Welcome new followers | src/welcomeNewFollowers.js |
x.com/USERNAME/followers |
Notification Manager
File: src/notificationManager.js
Manages X notifications: filter by type (mentions, likes, reposts, follows, replies), mark as read, and track notification activity.
How to Use
- Navigate to
x.com/notifications - Open DevTools (F12) -> Console
- Paste the script -> Enter
Configuration
const CONFIG = {
filterTypes: ['mentions', 'likes', 'reposts', 'follows'],
markAsRead: true,
scrollToLoadMore: true,
maxNotifications: 200,
actionDelay: 1000,
};
Features
- Filter notifications by type
- Count notifications by category
- Scrape notification content with author and timestamp
- Export notification data as JSON
- Identify most-engaged users from notifications
Notification Scraper
File: scripts/scrapeNotifications.js
Standalone scraper that exports all visible notifications as structured JSON with author, type, content, and timestamp.
DOM Selectors
| Element | Selector |
|---|---|
| Notification cells | [data-testid="notification"] |
| Toggle switch | [data-testid="settingsSwitch"] |
| Notifications tab | a[href="/notifications"] |
| Mentions tab | a[href="/notifications/mentions"] |
| Notification text | [data-testid="notification"] [dir="auto"] |
Strategy Guide
Identifying engagement opportunities
- Run
src/notificationManager.jsto filter for mentions - Identify high-value mentions (verified users, large accounts)
- Prioritize replies to mentions from users with 1000+ followers
- Use
src/engagementLeaderboard.jsto cross-reference top engagers
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.
- 2mo ago First seen · 87 lines · 43 tokens per session scan A 7889a804034e
notifications-management is a skill published in the GitHub repository nirholas/XActions (644 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 644 once invoked, about $0.0002 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-08-30.
notifications-management compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| notifications-managementnirholas/XActions | Skill | 644 | yesterday | Apache-2.0 | A | 43 | Claude Code |
| browser-automation-studioVrooli/Vrooli | Skill | 56 | 2d ago | AGPL-3.0 | A | 0 | Claude Code, Codex |
| slackvercel-labs/agent-browser | Skill | 46k | yesterday | Apache-2.0 | A | 88 | Claude Code |
| browser-usebrowser-use/browser-use | Skill | 120k | yesterday | MIT | A | 57 | Claude Code, Codex |
| Interceptordanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 93 | Claude Code, Codex |
| cli-anything-macrocliHKUDS/CLI-Anything | Skill | 58k | 1mo ago | Apache-2.0 | A | 67 | Claude Code, Codex |
| pinchtab-mcppinchtab/pinchtab | Skill | 11k | 10d ago | MIT | A | 52 | Claude Code, Codex |