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 commands/onesignal/onesignal-cursor-plugin/setup-onesignalgit 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/commands/onesignal/onesignal-cursor-plugin/setup-onesignal)<a href="https://agentmods.dev/commands/onesignal/onesignal-cursor-plugin/setup-onesignal"><img src="https://agentmods.dev/badge/commands/onesignal/onesignal-cursor-plugin/setup-onesignal.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.00017 | $0.00114 |
| Opus 5 | $0.00009 | $0.00057 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
setup-onesignal 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 3d 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
Help me set up the OneSignal Cursor plugin.
- Confirm Cursor has loaded the OneSignal plugin and MCP server.
- Follow the OneSignal OAuth prompt if Cursor asks to authenticate.
- Use the OneSignal MCP health/config/reference tools if available.
- If MCP tools are unavailable, guide me through local plugin install and Cursor reload steps.
- Do not ask me to paste OAuth tokens, API keys, or other secrets into chat.
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.
- 3d ago First seen · 13 lines · 17 tokens per session scan A 64c448dd3238
setup-onesignal is a command published in the GitHub repository OneSignal/onesignal-cursor-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 114 once invoked, about $0.0001 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.
Other commands, from other repositories
code-review-checklist
Comprehensive checklist for conducting thorough code reviews to ensure quality, security, and maintainability.
create-pr
Command "create-pr" from novuhq/novu, covering create pr and steps.
self-audit
Run npm run scan from the repository root. This repo must report L4 · Self-correcting.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.
sum
Distill insights from this conversation into memories.
search
Search Nowledge Mem for relevant memories.