configure-notifications

configure-notifications is a skill for Claude Code from naimkatiman/continuous-improvement. It costs 17 tokens per session (9,405 once invoked), scanned A, a copy of configure-notifications, MIT.

A setup guide for connecting OMC to Telegram, Discord, or Slack so it can send you notifications.

In plain words
What is it for?
It helps configure a messaging service, choose a provider, and save the connection settings for later use.
Why use it?
It removes the need to configure notification settings and credentials by hand. You can be alerted when a session ends, needs input, or finishes background work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/my-project.

Part of the oh-my-claudecode plugin — 36 skills, 17 agents shipped together

Good fit It helps configure a messaging service, choose a provider, and save the connection settings for later use.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add naimkatiman/continuous-improvement
Claude Code
/plugin install oh-my-claudecode

Made for: Claude Code.

Or install oh-my-claudecode, the plugin that ships this one along with the rest of its 36 skills, 17 agents.

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 configure-notifications

README.md
[![agentmods](https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/configure-notifications.svg)](https://agentmods.dev/skills/naimkatiman/continuous-improvement/configure-notifications)
Your own site
<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/configure-notifications"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/configure-notifications.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,405 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod 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.00017 $0.09405
Opus 5 $0.00009 $0.04702
Sonnet 5 $0.00003 $0.01881
Haiku 4.5 $0.00002 $0.00941

Measured today against content hash 0fde7b710487, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

configure-notifications 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 today.

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.

curl -s "https://api.telegram.org/bot${BOT_TOKEN}/getUpdates" | jq '.result[-1].message.chat.id // .result[-1].message.from.id // "No messages found - send /start to your bot first"'
Origin

This is a copy

92% identical to configure-notifications — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

third-party/oh-my-claudecode/skills/configure-notifications/SKILL.md · 1,215 lines

How it starts

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

Configure Notifications

Set up OMC notification integrations so you're alerted when sessions end, need input, or complete background tasks.

Routing

Detect which provider the user wants based on their request or argument:

  • If the trigger or argument contains "telegram" → follow the Telegram section
  • If the trigger or argument contains "discord" → follow the Discord section
  • If the trigger or argument contains "slack" → follow the Slack section
  • If no provider is specified, use AskUserQuestion:

Question: "Which notification service would you like to configure?"

Options:

  1. Telegram - Bot token + chat ID. Works on mobile and desktop.
  2. Discord - Webhook or bot token + channel ID.
  3. Slack - Incoming webhook URL.

Telegram Setup

Set up Telegram notifications so OMC can message you when sessions end, need input, or complete background tasks.

How This Skill Works

This is an interactive, natural-language configuration skill. Walk the user through setup by asking questions with AskUserQuestion. Write the result to ${CLAUDE_CONFIG_DIR:-~/.claude}/.omc-config.json.

Step 1: Detect Existing Configuration

CONFIG_FILE="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/.omc-config.json"

if [ -f "$CONFIG_FILE" ]; then
  HAS_TELEGRAM=$(jq -r '.notifications.telegram.enabled // false' "$CONFIG_FILE" 2>/dev/null)
  CHAT_ID=$(jq -r '.notifications.telegram.chatId // empty' "$CONFIG_FILE" 2>/dev/null)
  PARSE_MODE=$(jq -r '.notifications.telegram.parseMode // "Markdown"' "$CONFIG_FILE" 2>/dev/null)

  if [ "$HAS_TELEGRAM" = "true" ]; then
    echo "EXISTING_CONFIG=true"
    echo "CHAT_ID=$CHAT_ID"
    echo "PARSE_MODE=$PARSE_MODE"
  else
    echo "EXISTING_CONFIG=false"
  fi
else
  echo "NO_CONFIG_FILE"
fi

If existing config is found, show the user what's currently configured and ask if they want to update or reconfigure.

Step 2: Create a Telegram Bot

Guide the user through creating a bot if they don't have one:

Read the full file on GitHub · 1,215 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. today Changed 0fde7b710487
  2. 4d ago First seen · 1,215 lines · 17 tokens per session scan A 7c83ba8a36f8

Subscribe to this mod's changes

configure-notifications is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 9,405 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to configure-notifications, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

opensrc

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…

vercel-labs/opensrc · 103 tokens

nopus-configure

Configure nopus complexity sensitivity, extra-simple rewrites, rewrite evidence, and Pi response hiding for this user.

Vistyy/nopus · 27 tokens

nopus-simplify

Rewrite the immediately preceding assistant response with clearer and more direct prose when the user invokes this skill.

Vistyy/nopus · 25 tokens

agentpush

Bridge an imported agentpush MCP server (Telegram, WhatsApp, etc.) with live agentproto sessions via the daemon's transmitter subsystem: transmitmessage sends outbound and binds the recipient to a session, inboundwatcherstart polls agentpush for new messages, and inboundendpointcreate/POST /inbound(/:slug) route…

agentproto/ts · 119 tokens

bureau

Drive Bureau — the browser stack's installable capability server: a stealth Firefox (Camofox) + daemon that exposes browser tools as MCP-over-HTTP on :8830, plus a CLI for saved browser identities (sessions), social capture / search, adapter health probes, declarative workflows, and Guilde connection. Use when working…

agentproto/ts · 131 tokens

agentproto-apps

Operate and build Agentproto apps — AIP-42 app bundles (defineApp().emit(dir), APP.md + agents/ + workflows/ + ui/) and their daemon lifecycle (appinstall, appapply, apprun, appstatus, appstop) plus the app-scoped durable data plane (appdataread/write/list/migrate). Covers serving one with a UI (agentproto app serve →…

agentproto/ts · 178 tokens