Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSnpx agentmods add skills/dds-solutions/ai-tadpole-os/a2a-protocolWrote 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/dds-solutions/ai-tadpole-os/a2a-protocol)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/a2a-protocol"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/a2a-protocol/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/dds-solutions/ai-tadpole-os/a2a-protocol"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/a2a-protocol.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.00032 | $0.00802 |
| Opus 5.5 | $0.00013 | $0.00321 |
| Sonnet 5.5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
a2a-protocol 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / a2a-protocol
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Unauthorized budget overruns, invalid capability signatures, vault drainage.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Agent-to-Agent (A2A) Economic & Capability Protocol
Purpose: Govern inter-agent economic settlements, cryptographic capability delegation, and budget limits across the swarm. Workflow Binding: Used during
/orchestrateand/audit.
🎯 Progressive Disclosure & L3 Reference Index
Read REQUIRED core standards below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide / Tool | Purpose | Trigger / When to Load |
|---|---|---|
references/a2a_web3_vault_and_capabilities.md |
Web3 vault smart contract specs, key rotation window, hold-and-commit 2PC | Dispatching paid subagent missions or rotating keys |
scripts/capability_key_validator.py |
Deterministic budget cap validator and capability key format checker | Pre-dispatch mission budgeting or self-test verification |
🏛️ Core Architectural Invariants
- Two-Key Rotation Grace Period: The system must accept both
CAPABILITY_KEY_CURRandCAPABILITY_KEY_PREVduring scheduled key rotation windows. - Oversight Key Gate: Any subagent task demanding budget $> $50.00$ USD requires an explicit cryptographic signature from
OVERSIGHT_PUBLIC_KEY. - Escrow Hold-and-Commit: Web3 vault settlements must freeze funds on task dispatch and release on proof-of-work completion.
🛡️ Socratic Gate: Budget Authority & Cryptographic Verification
Before committing inter-agent financial transactions:
- Budget Allowance: Is the requested budget within the agent's authorized quota?
- Key Freshness: Is the capability key active or within the grace period?
- Idempotency: Is the transaction keyed with a unique UUID to prevent double-spending?
What ships with it
2 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.
- 12d ago First seen · 71 lines · 32 tokens per session scan A 09236943ba1f
a2a-protocol is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 802 once invoked, about $0.0001 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-18.
Other skills, from other repositories
walkeros-create-destination
Use when creating a new walkerOS destination to send events to a vendor or API (GA4/gtag, Meta/Facebook Pixel, Mixpanel, Amplitude, a custom HTTP API, Measurement Protocol), web or server-side. Example-driven workflow: research the vendor SDK and define step examples before implementing the destination interface, env…
walkeros-create-source
Use when creating a new walkerOS source to capture events (browser source, dataLayer interception, server/HTTP source, webhook receiver, event capture), web or server-side. Example-driven workflow: research the input format and define step examples before implementing the push interface, createTrigger, and env pattern.
implementing-mcp-tools
Guide for exposing PostHog product endpoints as MCP tools. Use when creating new or updating API endpoints, adding MCP tool definitions, scaffolding YAML configs, or writing serializers with good descriptions. Covers the full pipeline from Django serializer to generated TypeScript tool handler.
adopting-generated-api-types
Use when migrating frontend code from manual API client calls (api.get, api.create, api.surveys.get, api.dashboards.list, new ApiRequest()) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from lib/api, files with api.get . , manual interface definitions that…
adding-personhog-rpc
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC…
solana-toolkit-guide
Guide to the Solana Wallet Toolkit — vanity address generation with multi-threaded search, official Solana Labs libraries, Rust and TypeScript implementations. Includes wallet generation, custom address prefixes, and OG names on the blockchain.