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 business-adsgit 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/business-ads)<a href="https://agentmods.dev/skills/nirholas/xactions/business-ads"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/business-ads.svg" alt="Measured on agentmods" 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.00057 | $0.00679 |
| Opus 5 | $0.00028 | $0.00340 |
| Sonnet 5 | $0.00011 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
business-ads 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business & Ads Tools
Browser console scripts and automation for X/Twitter business intelligence and promotion.
Script Selection
| Goal | File | Navigate to |
|---|---|---|
| Brand monitoring & sentiment | src/businessTools.js |
Search results page |
| Audience insights | src/businessTools.js |
x.com/USERNAME/followers |
| Competitor comparison | src/businessTools.js |
Any profile page |
| A/B test tweet performance | src/tweetABTester.js |
x.com/USERNAME |
| Auto-plug viral tweets | src/autoPlugReplies.js |
x.com/USERNAME |
| Audience demographics | src/audienceDemographics.js |
x.com/USERNAME/followers |
| Content performance | src/tweetPerformance.js |
x.com/USERNAME |
Business Tools
File: src/businessTools.js
Puppeteer-based module for business intelligence.
Functions
| Function | Purpose |
|---|---|
monitorBrandMentions(page, brand, {limit, since}) |
Search mentions with sentiment |
getAudienceInsights(page, username, {sampleSize}) |
Follower bio analysis |
analyzeCompetitors(page, ['user1', 'user2']) |
Side-by-side comparison |
Tweet A/B Testing
File: src/tweetABTester.js
Test tweet variations with statistical comparison.
Controls: XActions.createTest(name, textA, textB), XActions.setUrl(name, variant, url), XActions.measure(name), XActions.results(name)
Auto-Plug Replies
File: src/autoPlugReplies.js
Automatically reply to your viral tweets with promotional content.
Controls: XActions.setPlug(text), XActions.setThreshold(n), XActions.scan(), XActions.autoScan(ms)
Strategy Guide
Low-budget promotion (no ads spend)
- A/B test content styles with
src/tweetABTester.js - Set up
src/autoPlugReplies.jsto promote on viral tweets - Find trends with
src/trendingTopicMonitor.jsfor timely content - Analyze audience with
src/audienceDemographics.jsfor targeting - Track results with
src/tweetPerformance.js
Brand monitoring
- Use
src/businessTools.js->monitorBrandMentions()for sentiment - Set up
src/keywordMonitor.jsfor real-time brand mention alerts - Export data for reporting
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.
- 8d ago First seen · 74 lines · 57 tokens per session scan A 5deefbb2e498
business-ads is a skill published in the GitHub repository nirholas/XActions (512 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 679 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…
bundle-integration-steer
Integrate scenarios/{{TARGET}}/ into the Vrooli Business Suite bundle so that it participates in subscription gating, credit-based metering, and authenticated downloads managed by the Landing Page Business Suite (LPBS) scenario.
leader-research-analyze-plan
Orchestrate the full lifecycle of ecosystem capability improvement: research the current state of skills and scenarios in a target area, analyze capability gaps with structured decision trees, and plan cross-cutting implementation that spans skills, scenarios, CLIs, and ecosystem registries. This pipeline composes…