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.
/plugin marketplace add RobinNorberg/oh-my-copilot/plugin install oh-my-copilotWrote 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/robinnorberg/oh-my-copilot/configure-notifications)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/configure-notifications"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/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.
<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/configure-notifications"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/configure-notifications.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.00017 | $0.09333 |
| Opus 5 | $0.00009 | $0.04666 |
| Sonnet 5 | $0.00003 | $0.01867 |
| Haiku 4.5 | $0.00002 | $0.00933 |
Grade B, and why
configure-notifications scanned grade B with 3 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 7d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
node -e "const[token,chatId,parseMode]=process.argv.slice(1);fetch('https://api.telegram.org/bot'+token+'/sendMessage',{method:'POST',headers:{'content-type':'application/x-www-form-urlencoded'},body:new URLSearchParams( Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
node -e "const[url,mention]=process.argv.slice(1);const text=(mention?mention+'\n':'')+'OMC test notification - Discord is configured';fetch(url,{method:'POST',headers:{'content-type':'application/json'},body:JSON.string Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
node -e "const{spawnSync}=require('node:child_process');const[cmd,...args]=process.argv.slice(1);const r=spawnSync(cmd,args.map(a=>a.split('{{event}}').join('test')),{encoding:'utf8',shell:process.platform==='win32'});pr This is a copy
92% identical to configure-notifications — 339 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.
How it starts
The opening of the file, as written. The whole thing — 1,056 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:
- Telegram - Bot token + chat ID. Works on mobile and desktop.
- Discord - Webhook or bot token + channel ID.
- Slack - Incoming webhook URL.
Shared Config Commands
Every provider section reads and writes the same ${COPILOT_CONFIG_DIR:-~/.copilot}/.omc-config.json.
These two commands are the only ones you need for that, and both run unchanged in bash,
zsh, and PowerShell — no jq, no shell-specific redirection.
READ_NOTIFICATIONS — print the current notifications object, or NO_CONFIG_FILE:
node -e "const p=require('path'),f=require('fs'),d=process.env.COPILOT_CONFIG_DIR||p.join(require('os').homedir(),'.copilot'),t=p.join(d,'.omc-config.json');if(f.existsSync(t)===false){console.log('NO_CONFIG_FILE');process.exit(0)}let c={};try{c=JSON.parse(f.readFileSync(t,'utf8'))}catch{console.log('INVALID_CONFIG_FILE');process.exit(0)}console.log(JSON.stringify(c.notifications||{},null,2))"
MERGE_CONFIG — deep-merge one JSON patch into the config. It writes through a temp file, so a failure can never truncate the user's existing settings, and it refuses to touch a config it cannot parse:
node -e "const p=require('path'),f=require('fs'),d=process.env.COPILOT_CONFIG_DIR||p.join(require('os').homedir(),'.copilot'),t=p.join(d,'.omc-config.json');const patch=JSON.parse(process.argv[1]);f.mkdirSync(p.dirname(t),{recursive:true});let c={};if(f.existsSync(t)){try{c=JSON.parse(f.readFileSync(t,'utf8'))}catch{console.error('ERROR: existing config is not valid JSON; it was not modified');process.exit(1)}}const merge=(a,b)=>{for(const k of Object.keys(b)){const v=b[k];if(v&&typeof v==='object'&&Array.isArray(v)===false){a[k]=merge(a[k]&&typeof a[k]==='object'?a[k]:{},v)}else{a[k]=v}}return a};merge(c,patch);const tmp=t+'.tmp';f.writeFileSync(tmp,JSON.stringify(c,null,2));f.renameSync(tmp,t);console.log('Updated '+t)" "{\"notifications\":{\"enabled\":true}}"
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.
- 7d ago Changed · -159 lines scan A → B c4f4539b100b
- 11d ago First seen · 1,215 lines · 17 tokens per session scan A 563ca6a5e67a
configure-notifications is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 9,333 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 3 findings (sends data to an external url, makes network calls, runs shell commands). It is 92% identical to configure-notifications, differing in 339 lines, and is treated as a copy.
Other skills, from other repositories
bulk-reader
Delegate fat file reads to the project's pmread worker. Use when a Read/cat/head/tail/sed of a file over pmread.minlines was blocked, or you must map a large file without ingesting it.
handoff
Checkpoint work for recovery — fires on "handoff", "wrap up", context pressure, a closed phase, or before a long external wait or irreversible gate. Part of the Agentsmith harness; writes durable state plus a paste-ready kickoff block so a fresh session loses nothing.
commitment-catcher
Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with…
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
inbox-triage
Sweeps the inbox, categorises every message as needs-reply-today, needs-reply-this-week, waiting-on-others, FYI or noise, creates reply drafts in the Drafts folder, and saves a dated triage report to OneDrive. Moves or archives mail only when a rule the user wrote in its rules file says so. Use when the user asks to…
meeting-prep-onepager
Builds a one-page meeting prep brief and saves it as a Word document in OneDrive. Gathers the calendar invite, recent email threads with attendees, Teams messages and shared files, then distils them into purpose, attendee positions, open threads, key files, talking points and risks. Use when the user asks to prepare…