a2a-setup

a2a-setup is a skill for Claude Code from OrcaQubits/agentic-commerce-skills-plugins. It costs 50 tokens per session (953 once invoked), scanned A, original, MIT.

A setup guide for starting an Agent2Agent (A2A) project, a system where separate agents communicate over a shared protocol. It creates a basic agent server, client, configuration, and Agent Card describing the agent.

In plain words
What is it for?
Use it to install an A2A software kit, create the project structure, define the Agent Card, and make a minimal server and client.
Why use it?
It removes the initial project scaffolding and configuration work needed before agents can discover and call one another.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the a2a-multi-agent plugin — 16 skills, 1 agent, 1 hook shipped together

Good fit Use it to install an A2A software kit, create the project structure, define the Agent Card, and make a minimal server and client.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup
Install

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.

Any agent
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill a2a-setup
Clone the repo
git clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-plugins

Made for: Claude Code.

Or install a2a-multi-agent, the plugin that ships this one along with the rest of its 16 skills, 1 agent, 1 hook.

Wrote 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.

agentmods badge for a2a-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup/github.svg)](https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup)
Your own site
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup/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.

agentmods 80×15 button for a2a-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 953 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00953
Opus 5.5 $0.00020 $0.00381
Sonnet 5.5 $0.00010 $0.00191
Haiku 4.5 $0.00005 $0.00095

Measured 1mo ago against content hash 6a1c0c7e3a78, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

a2a-setup 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 1mo 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.

a2a-multi-agent/skills/a2a-setup/SKILL.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

A2A Project Setup

Before writing code

Fetch live docs:

  1. Fetch https://a2a-protocol.org/latest/specification/ for the latest protocol overview
  2. Web-search site:github.com a2aproject a2a-python README or a2aproject a2a-js README for the target SDK's current installation and quickstart
  3. Web-search site:github.com a2aproject a2a-samples for official sample project structures
  4. Fetch the SDK's PyPI/npm page for the latest version number

Conceptual Architecture

What Setup Involves

A2A project setup creates the foundation for a multi-agent system:

  1. Install the A2A SDK for your language (Python, JS/TS, Go, Java, .NET)
  2. Create directory structure — agent server, client, Agent Card, configuration
  3. Define the Agent Card — the discovery document describing your agent
  4. Create a minimal server — HTTP endpoint that handles JSON-RPC 2.0 A2A methods
  5. Create a minimal client — code to discover and call another A2A agent

Python Project Structure

my-a2a-agent/
├── agent_card.json          # Agent Card (also served at /.well-known/agent-card.json)
├── server.py                # A2A server entry point
├── client.py                # A2A client for testing
├── agent/
│   ├── __init__.py
│   └── handler.py           # Task processing logic
├── pyproject.toml           # or requirements.txt
└── tests/
    └── test_agent.py

JS/TS Project Structure

my-a2a-agent/
├── agent-card.json
├── src/
│   ├── server.ts            # A2A server entry point
│   ├── client.ts            # A2A client for testing
│   └── handler.ts           # Task processing logic
├── package.json
├── tsconfig.json
└── tests/
    └── agent.test.ts

Agent Card Skeleton

Every A2A agent needs an Agent Card. Minimal structure:

{
  "name": "My Agent",
  "description": "What this agent does",
  "url": "http://localhost:8000",
  "version": "1.0.0",
  "protocolVersion": "0.2.1",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "stateTransitionHistory": false
  },
  "skills": [
    {
      "id": "skill-1",
      "name": "Skill Name",
      "description": "What this skill does",
      "tags": ["tag1", "tag2"],
      "examples": ["Example input"]
    }
  ],
  "defaultInputModes": ["text/plain"],
  "defaultOutputModes": ["text/plain"]
}

Read the full file on GitHub · 105 lines

Changes

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.

  1. 1mo ago First seen · 105 lines · 50 tokens per session scan A 6a1c0c7e3a78

Subscribe to this mod's changes

a2a-setup is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 953 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-08-30.

Related

Other skills, from other repositories

design-taste-frontend

Use for visual design direction on greenfield, user-facing surfaces — marketing and landing pages, generated apps, portfolio-style or standalone pages. NOT for routine Archestra platform UI work (dashboards, data tables, settings, forms, existing components) — use archestra-dev-frontend for that. Upstream intent…

archestra-ai/archestra · 0 tokens

archestra-docs-writer

Use when writing, editing, restructuring, or auditing Archestra documentation under docs/pages/ — new feature docs, page rewrites, sidebar and information-architecture changes, tone or copy fixes, diagrams, and docs screenshots.

archestra-ai/archestra · 51 tokens

archestra-dev-frontend

Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.

archestra-ai/archestra · 40 tokens

archestra-dev-testing

Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.

archestra-ai/archestra · 38 tokens

managing-archestra-releases

Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.

archestra-ai/archestra · 51 tokens

migrate-to-archestra

Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.

archestra-ai/archestra · 73 tokens