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 ap2-risk-signalsgit 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/ap2-risk-signals)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-risk-signals"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-risk-signals/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/orcaqubits/agentic-commerce-skills-plugins/ap2-risk-signals"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-risk-signals.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.00050 | $0.00925 |
| Opus 5 | $0.00025 | $0.00463 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
ap2-risk-signals 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 Risk Signals Framework
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/specification/for risk payload specification - Fetch
https://ap2-protocol.org/topics/privacy-and-security/for risk considerations - Web-search
ap2 protocol risk signals fraud agentic paymentsfor risk framework details - Web-search
site:github.com google-agentic-commerce AP2 riskfor implementation references
Conceptual Architecture
Why Risk Signals Matter
Agentic commerce introduces novel risk dimensions that traditional payment systems weren't designed for. AP2's risk signals framework provides a common language for all ecosystem participants to assess transaction risk.
Novel Agentic Risk Factors (from the official AP2 risk factor table)
| Risk Factor | Description |
|---|---|
| User asynchronicity | User may not be present during the entire transaction journey |
| Delegated trust | Agents initiate transactions on behalf of users |
| Mandate-merchant matching | Verifying the purchase matches the authorized intent |
| Temporal gaps | Time between token generation and payment execution |
| Indirect trust establishment | CP and Merchant may not have a direct trust relationship |
| Agent identity verification | Verifying the agent is who it claims to be |
Additional AI-Specific Risks (not from the official AP2 risk factor table)
The following are additional AI-specific risk considerations relevant to agentic commerce implementations, but they are not part of the official AP2 specification's novel risk factor table:
| Risk Factor | Description |
|---|---|
| Agent hallucination | AI agent may misinterpret user intent |
| Prompt injection | Malicious inputs that manipulate agent behavior |
Risk Payload
The risk payload is an open-ended field structure in V0.1:
- Intentionally flexible for industry-specific risk signals
- Allows Credentials Providers, Merchants, and Networks to pass custom risk data
- Each actor contributes their own risk assessment signals
- The payload travels with the mandate through the transaction flow
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.
- 10d ago First seen · 113 lines · 50 tokens per session scan A 3b9fc5ee7aa3
ap2-risk-signals is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 925 once invoked, about $0.0003 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
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
sales-ledger
Provides the Q3 sales ledger workbook for reporting tasks. Use when a task asks you to compute bonuses or totals over the sales ledger; the data lives only in this skill's bundled workbook.
okx-dapp-discovery
Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI…
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…