agentmods.dev

oh-my-codex: Skill for Codex

.codex/skills/configure-notifications/SKILL.md

configure-notifications is a skill for Codex from junghwaYang/oh-my-codex. It costs 0 tokens per session (586 once invoked), scanned A, original, MIT.

A setup tool for sending coding-session updates to Telegram, Discord, Slack, or a file.

In plain words
What is it for?
Use it to configure notification channels and choose which session events they report.
Why use it?
It lets you notice completed sessions, errors, and milestones without repeatedly checking the session.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: positional $N argument; reads ~/.codex paths; mentions Codex.

This is junghwaYang/oh-my-codex's own configuration. It tells Codex how to work on oh-my-codex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything oh-my-codex configures →

not rated 5repo 8mo ago A scan 0 tokens original MIT
View source ↗ junghwaYang/oh-my-codex
Reuse

Borrowing it

Nothing to install: this file belongs to junghwaYang/oh-my-codex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/junghwaYang/oh-my-codex/main/.codex/skills/configure-notifications/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/junghwaYang/oh-my-codex

Made for: 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 configure-notifications

README.md
[![agentmods](https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/configure-notifications/github.svg)](https://agentmods.dev/skills/junghwayang/oh-my-codex/configure-notifications)
Your own site
<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/configure-notifications"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/configure-notifications/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.

agentmods 80×15 button for configure-notifications

Your own site · 80×15
<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/configure-notifications"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/configure-notifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.00586
Opus 5.5 $0.00000 $0.00234
Sonnet 5.5 $0.00000 $0.00117
Haiku 4.5 $0.00000 $0.00059

Measured 2mo ago against content hash 00ad24242a28, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

configure-notifications 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 2mo 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.

.codex/skills/configure-notifications/SKILL.md · 115 lines

How it starts

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

Configure Notifications Skill

Set up notifications for session events.

Supported Channels

Channel Setup Required
Telegram Bot token + Chat ID
Discord Webhook URL
Slack Webhook URL
File Output path

Telegram Setup

1. Create Bot

  1. Message @BotFather on Telegram
  2. Send /newbot
  3. Follow prompts to get token

2. Get Chat ID

  1. Message your bot
  2. Visit: https://api.telegram.org/bot<TOKEN>/getUpdates
  3. Find chat.id in response

3. Configure

omx config-notify telegram \
  --token "123456:ABC-DEF" \
  --chat-id "-1001234567890"

Discord Setup

1. Create Webhook

  1. Server Settings → Integrations → Webhooks
  2. Create new webhook
  3. Copy URL

2. Configure

omx config-notify discord \
  --webhook "https://discord.com/api/webhooks/..."

Configuration File

~/.codex/notifications.toml

[telegram]
enabled = true
token = "123456:ABC-DEF"
chat_id = "-1001234567890"
events = ["session_complete", "error", "milestone"]
tag_list = ["@username"]

[discord]
enabled = true
webhook = "https://discord.com/api/webhooks/..."
events = ["session_complete", "error"]
tag_list = ["@here", "123456789"]

[file]
enabled = false
path = "~/.codex/notifications.log"

Event Types

Event When
session_start Orchestration begins
session_complete Orchestration ends
milestone Significant progress
error Failure occurred
warning Potential issue

Tag Options

Telegram

  • @username - Mention user

Discord

  • @here - Notify online members
  • @everyone - Notify all
  • 123456789 - User ID
  • role:987654321 - Role ID

Usage

configure-notifications: set up Telegram alerts

configure-notifications: add Discord webhook

configure-notifications: enable file logging

Message Format

## 🚀 Session Complete

**Task:** Build auth system
**Duration:** 15m 23s
**Status:** ✅ Success
**Tokens:** 45,234 (~$0.15)

### Summary
- Implemented login/logout
- Added JWT validation
- Created user endpoints

Read the full file on GitHub · 115 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. 2mo ago First seen · 115 lines · 0 tokens per session scan A 00ad24242a28

Subscribe to this mod's changes

configure-notifications is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 586 tokens. 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.

Related

configure-notifications compared with skills from other repositories

configure-notifications next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
configure-notificationsjunghwaYang/oh-my-codexSkill58mo agoMITA0Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code