unified-notifications-ops

unified-notifications-ops is a skill for Claude Code, Codex from JunMystery/Agent-Guidance-Python. It costs 49 tokens per session (1,237 once invoked), scanned A, original, MIT.

A workflow for bringing alerts from code hosting, project tracking, local tools, and communication apps into one organized stream.

In plain words
What is it for?
Use it to route and consolidate pull-request reviews, CI failures, issue changes, local tool events, desktop alerts, chat, and email notifications.
Why use it?
It reduces scattered, duplicate, and noisy alerts by giving each event a clear urgency, owner, destination, and next action.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex; mentions OpenCode.

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/junmystery/agent-guidance-python/unified-notifications-ops
Any agent
npx skills add JunMystery/Agent-Guidance-Python --skill unified-notifications-ops
Clone the repo
git clone --depth 1 https://github.com/JunMystery/Agent-Guidance-Python

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 unified-notifications-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/unified-notifications-ops.svg)](https://agentmods.dev/skills/junmystery/agent-guidance-python/unified-notifications-ops)
Your own site
<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/unified-notifications-ops"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/unified-notifications-ops.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,237 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.00049 $0.01237
Opus 5 $0.00024 $0.00619
Sonnet 5 $0.00010 $0.00247
Haiku 4.5 $0.00005 $0.00124

Measured 2d ago against content hash d9c2d6076621, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

unified-notifications-ops 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 2d 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/unified-notifications-ops/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Unified Notifications Ops

Use this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.

The job is to turn scattered events into one operator surface with:

  • clear severity
  • clear ownership
  • clear routing
  • clear follow-up action

When to Use

  • the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email
  • CI failures, review requests, issue updates, and operator events are arriving in disconnected places
  • the current setup creates noise instead of action
  • the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane
  • the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy

Preferred Surface

Start from what already exists:

  • GitHub issues, PRs, reviews, comments, and CI
  • Linear issue/project movement
  • local hook events and session lifecycle signals
  • desktop notification primitives
  • connected email/chat surfaces when they actually exist

Prefer ECC-native orchestration over telling the user to adopt a separate notification product.

Non-Negotiable Rules

  • never expose tokens, secrets, webhook secrets, or internal identifiers
  • separate:
    • event source
    • severity
    • routing channel
    • operator action
  • default to digest-first when interruption cost is unclear
  • do not fan out every event to every channel
  • if the real fix is better issue triage, hook policy, or project flow, say so explicitly

Event Pipeline

Treat the lane as:

  1. Capture the event
  2. Classify urgency and owner
  3. Route to the correct channel
  4. Collapse duplicates and low-signal churn
  5. Attach the next operator action

The goal is fewer, better notifications.

Default Severity Model

Class Examples Default handling
Critical broken default-branch CI, security issue, blocked release, failed deploy interrupt now
High review requested, failing PR, owner-blocking handoff same-day alert
Medium issue state changes, notable comments, backlog movement digest or queue
Low repeat successes, routine churn, redundant lifecycle markers suppress or fold

Read the full file on GitHub · 188 lines

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. 2d ago First seen · 188 lines · 49 tokens per session scan A d9c2d6076621

Subscribe to this mod's changes

unified-notifications-ops is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,237 once invoked, about $0.0002 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-09-03.