AccessiWeather: Skill for Codex

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

configure-notifications is a skill for Codex from Orinks/AccessiWeather. It costs 18 tokens per session (2,746 once invoked), scanned A, original, MIT.

A single setup workflow for configuring OMX notifications through Discord, Telegram, Slack, or custom commands.

In plain words
What is it for?
It is for enabling notification services, choosing notification detail levels, and configuring custom webhook or command-based notifications.
Why use it?
It avoids having separate setup paths for each notification service and provides one place to inspect current notification settings.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: names the AskUserQuestion tool; mentions Codex; built for openclaw.

This is Orinks/AccessiWeather's own configuration. It tells Codex how to work on AccessiWeather 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 AccessiWeather configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Orinks/AccessiWeather. 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/Orinks/AccessiWeather/main/.codex/skills/configure-notifications/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Orinks/AccessiWeather

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/orinks/accessiweather/configure-notifications/github.svg)](https://agentmods.dev/skills/orinks/accessiweather/configure-notifications)
Your own site
<a href="https://agentmods.dev/skills/orinks/accessiweather/configure-notifications"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/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/orinks/accessiweather/configure-notifications"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/configure-notifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,746 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00018 $0.02746
Opus 5 $0.00009 $0.01373
Sonnet 5 $0.00004 $0.00549
Haiku 4.5 $0.00002 $0.00275

Measured 9d ago against content hash e7dd8b2f3ad4, 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 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 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.

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 · 288 lines

How it starts

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

Configure OMX Notifications

Unified and only entry point for notification setup.

  • Native integrations (first-class): Discord, Telegram, Slack
  • Generic extensibility integrations: custom_webhook_command, custom_cli_command

Standalone configure skills (configure-discord, configure-telegram, configure-slack, configure-openclaw) are removed.

Step 1: Inspect Current State

CONFIG_FILE="$HOME/.codex/.omx-config.json"

if [ -f "$CONFIG_FILE" ]; then
  jq -r '
    {
      notifications_enabled: (.notifications.enabled // false),
      discord: (.notifications.discord.enabled // false),
      discord_bot: (.notifications["discord-bot"].enabled // false),
      telegram: (.notifications.telegram.enabled // false),
      slack: (.notifications.slack.enabled // false),
      openclaw: (.notifications.openclaw.enabled // false),
      custom_webhook_command: (.notifications.custom_webhook_command.enabled // false),
      custom_cli_command: (.notifications.custom_cli_command.enabled // false),
      verbosity: (.notifications.verbosity // "session"),
      idleCooldownSeconds: (.notifications.idleCooldownSeconds // 60),
      reply_enabled: (.notifications.reply.enabled // false)
    }
  ' "$CONFIG_FILE"
else
  echo "NO_CONFIG_FILE"
fi

Step 2: Main Menu

Use AskUserQuestion:

Question: "What would you like to configure?"

Options:

  1. Discord (native) - webhook or bot
  2. Telegram (native) - bot token + chat id
  3. Slack (native) - incoming webhook
  4. Generic webhook command - custom_webhook_command
  5. Generic CLI command - custom_cli_command
  6. Cross-cutting settings - verbosity, idle cooldown, profiles, reply listener
  7. Disable all notifications - set notifications.enabled = false

Step 3: Configure Native Platforms (Discord / Telegram / Slack)

Collect and validate platform-specific values, then write directly under native keys:

  • Discord webhook: notifications.discord
  • Discord bot: notifications["discord-bot"]
  • Telegram: notifications.telegram
  • Slack: notifications.slack

Read the full file on GitHub · 288 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. 9d ago First seen · 288 lines · 18 tokens per session scan A e7dd8b2f3ad4

Subscribe to this mod's changes

configure-notifications is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 2,746 once invoked, about $0.0001 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-08-30.