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 ComeOnOliver/skillshub --skill axiom-push-notifications-diaggit clone --depth 1 https://github.com/ComeOnOliver/skillshubWrote 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/comeonoliver/skillshub/axiom-push-notifications-diag)<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-push-notifications-diag"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-push-notifications-diag/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/comeonoliver/skillshub/axiom-push-notifications-diag"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-push-notifications-diag.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.00072 | $0.05568 |
| Opus 5 | $0.00036 | $0.02784 |
| Sonnet 5 | $0.00014 | $0.01114 |
| Haiku 4.5 | $0.00007 | $0.00557 |
Grade A, and why
axiom-push-notifications-diag scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| "The server says their payload is fine" | 55% of push failures are client-side (entitlements + tokens). Verify independently with curl. | 1-2 hours of finger-pointing before someone checks | How it starts
The opening of the file, as written. The whole thing — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push Notification Diagnostics
Systematic troubleshooting for push notification failures: missing notifications, token registration errors, environment mismatches, silent push throttling, and service extension problems.
Overview
Core Principle: When push notifications don't work, the problem is usually:
- Token/registration failures (never registered, wrong format, expired) — 30%
- Entitlement/provisioning mismatch (capability missing, wrong environment) — 25%
- Payload structure errors (missing keys, wrong types, invalid JSON) — 15%
- Focus/interruption suppression (iOS 15+ filtering, provisional auth) — 15%
- Service extension failures (timeout, crash, missing mutable-content) — 10%
- Delivery timing/throttling (silent push budget, APNs coalescing) — 5%
Always verify entitlements and token registration BEFORE debugging payload or delivery logic.
Red Flags
Symptoms that indicate push-specific issues:
| Symptom | Likely Cause |
|---|---|
| No notifications at all | Missing Push Notification capability or provisioning profile |
| Works in dev, not production | Sending to sandbox APNs with production token (or vice versa) |
| Token registration fails on Simulator | Expected — Simulator cannot register for remote notifications |
| Notifications appear without sound | Missing .sound in authorization options or payload |
| Rich notification shows plain text | Missing mutable-content: 1 in payload |
| Image not showing in notification | Service extension failed silently — check serviceExtensionTimeWillExpire |
| Silent push not waking app | System throttling (~2-3/hour), or app was force-quit by user |
| Notifications stopped after iOS update | Focus mode enabled by default in iOS 15+; check interruption level |
| Badge shows wrong number | Multiple notifications sent without explicit badge count reset |
| Actions not appearing | Category identifier mismatch between payload and registered categories |
| Notification appears twice | Both local and remote notification scheduled for same event |
| FCM works on Android, not iOS | Missing APNs auth key upload in Firebase Console |
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.
- 9d ago First seen · 534 lines · 72 tokens per session scan A 889a255ee1a3
axiom-push-notifications-diag is a skill published in the GitHub repository ComeOnOliver/skillshub (63 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 5,568 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
cmd_flutter_build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
cmd_gradle_build
Fix Gradle build errors for Android and KMP projects.
agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
swift-actor-persistence
Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.