agentmods.dev

onesignal-setup

onesignal-setup is a skill for Claude Code, Codex from OneSignal/onesignal-cursor-plugin. It costs 70 tokens per session (483 once invoked), scanned A, original, MIT.

A setup and troubleshooting guide for connecting the OneSignal Cursor plugin to OneSignal through a hosted MCP server. OneSignal is a service for sending notifications and managing messaging subscriptions.

In plain words
What is it for?
Use it to install, configure, authenticate, test, or troubleshoot the OneSignal plugin and its MCP connection.
Why use it?
It explains the first-run connection process, including OAuth sign-in and Cursor reloads, while keeping tokens and other credentials out of chat and source files.

Skill for Claude CodeCodex

not rated 0 1mo ago A scan 70 tokens original MIT
View the source file OneSignal/onesignal-cursor-plugin onesignal.com
Install

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.

agentmods
npx agentmods add skills/onesignal/onesignal-cursor-plugin/onesignal-setup
Any agent
npx skills add OneSignal/onesignal-cursor-plugin --skill onesignal-setup
Clone the repo
git clone --depth 1 https://github.com/OneSignal/onesignal-cursor-plugin

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for onesignal-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/onesignal/onesignal-cursor-plugin/onesignal-setup.svg)](https://agentmods.dev/skills/onesignal/onesignal-cursor-plugin/onesignal-setup)
Your own site
<a href="https://agentmods.dev/skills/onesignal/onesignal-cursor-plugin/onesignal-setup"><img src="https://agentmods.dev/badge/skills/onesignal/onesignal-cursor-plugin/onesignal-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00483
Opus 5 $0.00035 $0.00242
Sonnet 5 $0.00014 $0.00097
Haiku 4.5 $0.00007 $0.00048

Measured 4d ago against content hash 70e2d38b18bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

onesignal-setup 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 4d 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.

skills/onesignal-setup/SKILL.md · 62 lines

What it actually says

OneSignal Cursor Plugin Setup

Purpose

Help the user connect Cursor to OneSignal through the hosted OneSignal MCP server.

This plugin uses OAuth through the hosted OneSignal MCP server.

Required Setup

The user needs:

  • Cursor with plugin support.
  • A OneSignal account.

Authentication Guidance

Tell users to follow Cursor's OAuth prompt for the OneSignal MCP server. Never ask users to paste OAuth tokens, API keys, private keys, or credentials into chat, source files, rules, skills, commits, screenshots, or issue reports.

If Cursor was already open when the plugin was installed or updated, ask the user to reload Cursor with Developer: Reload Window or fully restart Cursor.

First Test

Use a read-only or utility MCP tool first. Prefer:

  • onesignal_health
  • onesignal_config
  • onesignal_reference_overview

Do not start with message sends, segment updates, template updates, Journey creation, exports, or subscription transfers.

Troubleshooting

If tools do not appear:

  1. Confirm the plugin is installed or symlinked into ~/.cursor/plugins/local/onesignal.
  2. Confirm .cursor-plugin/plugin.json is at the plugin root.
  3. Confirm mcp.json has a top-level mcpServers object.
  4. Reload Cursor.
  5. Check Cursor's MCP logs from the Output panel.

If tools appear but calls fail:

  1. Confirm the user completed the OneSignal OAuth flow in Cursor.
  2. Confirm the account has access to OneSignal MCP.
  3. Check whether the server URL is https://api.onesignal.com/mcp/oauth.
  4. Retry with a read-only utility tool.

Safety Defaults

For any write or send operation:

  • Prefer test users and narrow test audiences.
  • Summarize audience, content, timing, and expected effect.
  • Require explicit user approval before running the tool.
  • Add an extra confirmation for large audiences, production sends, deletes, or irreversible operations.
Changes

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.

  1. 4d ago First seen · 62 lines · 70 tokens per session scan A 70e2d38b18bc

Subscribe to this mod's changes

onesignal-setup is a skill published in the GitHub repository OneSignal/onesignal-cursor-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 483 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-31.

Backend and APIscursor-pluginmcponesignalpush-notifications
Related

Other skills, from other repositories

novu-inbox-integration

Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy…

novuhq/novu · 111 tokens

react-email

Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.

novuhq/novu · 30 tokens

address-pr-review

Critically triage pull request review comments against PR requirements and codebase reality, implement only valid fixes, and reply only when declining a suggestion. Use when the user asks to address PR comments, review feedback, CodeRabbit/Bugbot threads, or /address-pr-review.

novuhq/novu · 59 tokens

nv-onboard-dcr-mcp

Onboard a new DCR OAuth MCP catalog entry with provider-doc vetting and curl probes. Use when adding or changing mode: dcr entries in MCPSERVERS. Abort if the provider requires whitelist or manual approval.

novuhq/novu · 0 tokens

novu-manage-preferences

Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel…

novuhq/novu · 76 tokens

add-channel-whats-next-onboarding

Add a new chat channel's layer-2 dashboard onboarding — the connected-state "What's next" / "FOR YOUR USERS" developer-rollout guide plus its connected details page — in apps/dashboard, following the existing Slack, MS Teams, and Telegram pattern. Use when a connected agent integration needs a per-provider "what's…

novuhq/novu · 116 tokens