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 team-telnyx/ai --skill push-notification-testergit clone --depth 1 https://github.com/team-telnyx/aiWrote 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/team-telnyx/ai/push-notification-tester)<a href="https://agentmods.dev/skills/team-telnyx/ai/push-notification-tester"><img src="https://agentmods.dev/badge/skills/team-telnyx/ai/push-notification-tester/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/team-telnyx/ai/push-notification-tester"><img src="https://agentmods.dev/badge/skills/team-telnyx/ai/push-notification-tester.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.00055 | $0.00607 |
| Opus 5.5 | $0.00022 | $0.00243 |
| Sonnet 5.5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
push-notification-tester 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 1mo 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
Push Notification Tester
Send test VoIP push notifications to iOS (APNs) and Android (FCM) devices.
iOS (APNs)
node {baseDir}/scripts/send-ios-push.js \
--token=<device_token> \
--bundle-id=<bundle_id> \
--cert=<path/to/cert.pem> \
--key=<path/to/key.pem> \
[--env=sandbox|production] \
[--caller-name="Test Caller"] \
[--caller-number="+1234567890"]
Required args
--token— 64-char hex APNs device token--bundle-id— App bundle ID (e.g.com.telnyx.webrtc)--cert— Path to certificate PEM file--key— Path to private key PEM file
Optional args
--env—sandbox(default) orproduction--caller-name— Display name (default: "Test Caller")--caller-number— Phone number (default: "+1234567890")
Android (FCM)
node {baseDir}/scripts/send-android-push.js \
--token=<fcm_token> \
--project-id=<firebase_project_id> \
--service-account=<path/to/service-account.json> \
[--caller-name="Test Caller"] \
[--caller-number="+1234567890"]
Required args
--token— FCM device token--project-id— Firebase project ID--service-account— Path to service account JSON file
Optional args
--caller-name— Display name (default: "Test Caller")--caller-number— Phone number (default: "+1234567890")
Output
Both scripts output JSON to stdout:
{"success": true, "message": "Push notification sent successfully", "details": {...}}
{"success": false, "error": "Description of what went wrong"}
Exit code 0 on success, 1 on failure.
Dependencies
Run npm install in the scripts/ directory, or the scripts will auto-install on first run.
@parse/node-apn— APNs client for iOSgoogle-auth-library— Google OAuth for FCMaxios— HTTP client for FCM API
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 79 lines · 55 tokens per session scan A 5690d1b25c99
push-notification-tester is a skill published in the GitHub repository team-telnyx/ai (224 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 607 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-09-05.
Other skills, from other repositories
jetpack-compose-performance
Diagnose and optimize Android Jetpack Compose UI code. Use this skill when analyzing performance bottlenecks of existing code to minimize recomposition overhead and prevent dropped frames and UI lag.
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
axiom-audit-icloud
Use when the user mentions iCloud sync issues, CloudKit errors, ubiquitous container problems, or asks to audit cloud sync.
axiom-tools
Use when asking about Axiom skills or axbuild build/test capture, xclog console, xcsym .ips/MetricKit/.crash symbolication, xcui simulator UI/accessibility, or xcprof xctrace/CPU profiles.
spm-build-analysis
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build…