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 OrcaQubits/agentic-commerce-skills-plugins --skill a2a-push-notificationsgit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/a2a-push-notifications)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-push-notifications"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-push-notifications.svg" alt="Measured on agentmods" 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.00040 | $0.00859 |
| Opus 5 | $0.00020 | $0.00430 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
a2a-push-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 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.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A2A Push Notifications
Before writing code
Fetch live docs:
- Fetch
https://a2a-protocol.org/latest/specification/for the push notification section - Web-search
site:github.com a2aproject A2A push notificationsfor notification protocol details - Web-search
site:github.com a2aproject a2a-samples push notificationfor implementation examples - Fetch SDK docs for push notification classes and configuration
Conceptual Architecture
What Push Notifications Are
Push notifications allow A2A servers to proactively notify clients about task state changes without requiring the client to hold open a streaming connection or poll. The client registers a callback URL, and the server POSTs updates to it.
When to Use Push Notifications
- Very long-running tasks — Minutes to hours, where holding an SSE connection is impractical
- Asynchronous workflows — Client doesn't need real-time updates, just eventual notification
- Serverless clients — Clients that can't maintain long-lived connections
- Batch processing — Multiple tasks submitted, notifications received as each completes
How It Works
- Client registers — Calls
tasks/pushNotificationConfig/setwith a callback URL for a task - Server stores config — Associates the callback URL with the task
- Task progresses — Server processes the task normally
- Server notifies — When the task state changes, server POSTs an update to the callback URL
- Client processes — Client's webhook endpoint receives and processes the notification
Push Notification Methods
| Method | Purpose |
|---|---|
tasks/pushNotificationConfig/set |
Register a callback URL for a task |
tasks/pushNotificationConfig/get |
Retrieve the notification config for a task |
tasks/pushNotificationConfig/list |
List all notification configs |
tasks/pushNotificationConfig/delete |
Remove a notification config |
Notification Payload
When the server sends a push notification, it POSTs a JSON payload to the callback URL containing:
- Task ID
- Current task status (state + optional message)
- Optional artifacts or data
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 First seen · 91 lines · 40 tokens per session scan A 424e19a6b597
a2a-push-notifications is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 859 once invoked, about $0.0002 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.
Other skills, from other repositories
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…
archestra-dev-llm-providers
Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.
arwp-agent-discovery
Add or repair machine-readable agent discovery and interoperability surfaces for a website. Use when asked to expose llms.txt, AGENTS.md, Agent Skills, ARD, MCP, A2A, WebMCP, OpenAPI, API catalogs, agent-readable sitemaps, or an ARWP site profile. Discover what the site truly supports, prefer upstream standards, and…