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.
npx skills add terrylica/cc-skills --skill emergency-priority2-receiptgit clone --depth 1 https://github.com/terrylica/cc-skillsWrote 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/terrylica/cc-skills/emergency-priority2-receipt)<a href="https://agentmods.dev/skills/terrylica/cc-skills/emergency-priority2-receipt"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/emergency-priority2-receipt/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/terrylica/cc-skills/emergency-priority2-receipt"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/emergency-priority2-receipt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.00535 |
| Opus 5 | $0.00053 | $0.00267 |
| Sonnet 5 | $0.00021 | $0.00107 |
| Haiku 4.5 | $0.00011 | $0.00053 |
Grade A, and why
emergency-priority2-receipt 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 5d 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.
What it actually says
emergency-priority2-receipt
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Priority-2 emergency notification with receipt polling, via the TS core pushover_core.ts emergency.
env -u HTTPS_PROXY -u HTTP_PROXY bun "$(cc-plugin-root pushover-commander)/skills/_lib/pushover_core.ts" emergency \
--title "Title" --message "what happened + the one action needed" \
[--retry 30] [--expire 300] [--sound piano] [--attach report.png] [--app main|test]
Behavior (verified on a physical device 2026-05-30)
- priority 2 requires
retry(≥ 30 s) andexpire(≤ 10800 s) — Pushover returns HTTP 400 without them. The core supplies defaults (30 / 300) automatically. - The response returns a
receipt; the core polls/1/receipts/{receipt}.jsonevery 5 s and prints{acknowledged, acknowledged_at, expired}when you ack (verified ack at t+35 s) or it expires. sound=pianois a custom sound on this account;pianobaris the built-in fallback — usecustom-sounds resolve piano pianobar.- Attach a
render-incident-report-imagePNG for full detail; keep--message≤ 1024.
Post-Execution Reflection
After this skill completes, check before closing:
- Did the priority-2 alert repeat until acknowledged? If it stopped early or never fired, fix the retry/expire handling.
- Did the receipt poll detect the ack or expiry? If polling hung or missed the ack, fix the poll loop.
Only update if the issue is real and reproducible — not speculative.
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.
- 5d ago First seen · 33 lines · 106 tokens per session scan A 31312246b395
emergency-priority2-receipt is a skill published in the GitHub repository terrylica/cc-skills (72 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 535 once invoked, about $0.0005 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-05.
Other skills, from other repositories
session-status
Analyzes current session state without any cleanup. Full mode (default): resolves the active plan file, reads plan checklist + TaskList, gathers unfinished work/issues from conversation history, and emits a /handoff-built next-session prompt. Mid-session mode (/session-status mid): a fast plain-language 'done vs…
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
calendar
Google Calendar integration — check schedule, create events, daily briefings, proactive reminders. Triggers on "what's on my calendar", "add to calendar", "schedule a meeting", "when am I free", "daily briefing", or any calendar-related request.
native-first
Stack-agnostic discovery playbook for finding the native, non-custom way to do something before writing any script or wrapper. Use when tempted to write a shell/python/glue script, add a dependency, or build a custom helper — and whenever a script-guards hook blocks a script write. Climbs a fixed ladder (tool's own…
configure
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.