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 CATWILLgh/MAINFRAME --skill mainframe-notificationsgit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWrote 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/catwillgh/mainframe/mainframe-notifications)<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-notifications"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-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/catwillgh/mainframe/mainframe-notifications"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-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.00052 | $0.00656 |
| Opus 5.5 | $0.00021 | $0.00262 |
| Sonnet 5.5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
mainframe-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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application notifications
Deliver the working event-to-recipient flow and its administrative controls in the receiving application's stack and design system. Use only the channels the project needs; do not introduce a broker, new framework, chatbot agent or all five channels just because this method describes them. A settings screenshot or successful HTTP call is not end-to-end acceptance.
Inspect existing events, transactions, jobs, identities/tenants, settings, authorization, session/CSRF controls, secrets, UI and tests. Establish which events reach which recipients, content sensitivity, acceptable loss/duplication/delay, and actual provider capability. Reuse established decisions; ask for unresolved policy that changes access, external disclosure or delivery guarantees. Development authority does not itself authorize messages to real recipients, registration of external bots or production credential rotation.
Load by current decision
- Delivery: event contract, durability, retries, isolation, pause behavior, ordering and honest outcome states.
- Settings and interface: page outcome, master/channel switches, events, templates, recipients, secret updates and distinct actions.
- Bitrix24: portal webhook versus bot-token auth, registration, messages, optional event consumption and recovery.
- Telegram: Bot API delivery and channel constraints.
- Webhook: an independent outbound integration channel, signed delivery, recipient contract and endpoint security.
- Email: submission security, partial acceptance and retries.
- Web Push: browser subscriptions, ownership and receipts.
- Verification: failure scenarios, rendered UI and authorized channel acceptance. Each channel reference links its primary sources.
Use the appropriate engineering method for code and mainframe-testing for test
boundaries. Use mainframe-secrets for actual credential delivery. Infrastructure
changes belong to mainframe-infrastructure, within the existing task authority.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 60 lines · 52 tokens per session scan A 4103d77fb34d
mainframe-notifications is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 656 once invoked, about $0.0002 per session on Opus 5.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-10-07.
Other skills, from other repositories
cmux-backend
Backend TypeScript and Cloud VM development rules for cmux. Use when editing web/app/api, web/services, backend scripts, Cloud VM lifecycle, provider integrations, Postgres, Stack Auth pricing gates, migrations, or provider image build scripts.
cmux-socket-policy
Socket command threading and focus policy for cmux CLI/socket work. Use when adding or changing socket commands, CLI commands, telemetry commands, focus/select/open/close/send-key behavior, or automation that could steal app focus.
build-a-stripe-integration
Write Stripe code against what the API does today — plan the product shape, confirm every parameter from Stripe's own docs and schemas, and keep the agent in a sandbox. Use when adding checkout, billing, subscriptions, invoicing, or webhooks to a codebase, or when debugging Stripe integration code that compiles but…
auth-architect
Implement authentication and authorization with OWASP Top 10 standards, OAuth 2.0 + OIDC, WebAuthn/Passkeys, session management, and RBAC/ABAC. Use when user asks to implement login, signup, authentication, authorization, JWT, OAuth, SSO, passkeys, MFA, or role-based access. Do NOT use for API key management (use…
api-forge
Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency. Use when user asks to design an API, create endpoints, define REST/GraphQL schema, or generate OpenAPI spec. Do NOT use for database schema design, frontend API integration, or non-HTTP protocols (gRPC…
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.