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 OneSignal/onesignal-cursor-plugin --skill onesignal-setupgit clone --depth 1 https://github.com/OneSignal/onesignal-cursor-pluginWrote 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/onesignal/onesignal-cursor-plugin/onesignal-setup)<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/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/onesignal/onesignal-cursor-plugin/onesignal-setup"><img src="https://agentmods.dev/badge/skills/onesignal/onesignal-cursor-plugin/onesignal-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00070 | $0.00483 |
| Opus 5.5 | $0.00028 | $0.00193 |
| Sonnet 5.5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00048 |
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 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.
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_healthonesignal_configonesignal_reference_overview
Do not start with message sends, segment updates, template updates, Journey creation, exports, or subscription transfers.
Troubleshooting
If tools do not appear:
- Confirm the plugin is installed or symlinked into
~/.cursor/plugins/local/onesignal. - Confirm
.cursor-plugin/plugin.jsonis at the plugin root. - Confirm
mcp.jsonhas a top-levelmcpServersobject. - Reload Cursor.
- Check Cursor's MCP logs from the Output panel.
If tools appear but calls fail:
- Confirm the user completed the OneSignal OAuth flow in Cursor.
- Confirm the account has access to OneSignal MCP.
- Check whether the server URL is
https://api.onesignal.com/mcp/oauth. - 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.
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 · 62 lines · 70 tokens per session scan A 70e2d38b18bc
onesignal-setup is a skill published in the GitHub repository OneSignal/onesignal-cursor-plugin (0 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 483 once invoked, about $0.0003 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-31.
Other skills, from other repositories
novu-manage-subscribers
Create, update, search, and delete subscribers in Novu. Manage topics for group-based notification targeting. Set subscriber credentials for push and chat channels. Use when managing notification recipients, creating subscriber records, organizing subscribers into topics, or configuring channel-specific credentials.
novu-trigger-notification
Trigger Novu notification workflows to send messages across email, SMS, push, chat, and in-app channels. Supports single triggers, bulk triggers, broadcast to all subscribers, topic-based targeting, and cancellation. Use when sending transactional notifications, alerts, or any event-driven messages.
novu-framework-integration
Build code-first notification workflows with @novu/framework. Use when defining workflows in TypeScript (Zod / JSON Schema / Class Validator), composing channel steps (email, SMS, push, chat, in-app) with action steps (delay, digest, custom), exposing Step Controls for non-technical teammates, rendering…
consuming-endpoints-from-client-code
Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL codename vs insight breakdown property), handling rate-limit and materialised-endpoint error…
setting-up-a-custom-rest-source
Connect an arbitrary REST API to the PostHog data warehouse as a Custom source by authoring a JSON manifest, with no per-source code. Use when the user points at an API that has no built-in PostHog connector — "import data from this REST API", "sync my internal API", "connect this API from its docs", "build a custom…
instrument-tracing
Add PostHog distributed tracing to see how requests flow through services and where time goes. Use after implementing features or reviewing PRs to ensure request entry points, outbound calls, and background jobs produce spans, or when asked to add tracing or spans. Also handles pointing existing OpenTelemetry tracing…