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-agent-cardgit 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-agent-card)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-agent-card"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-agent-card/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/a2a-agent-card"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-agent-card.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.00042 | $0.00924 |
| Opus 5 | $0.00021 | $0.00462 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
a2a-agent-card 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A2A Agent Card
Before writing code
Fetch live docs:
- Fetch
https://a2a-protocol.org/latest/specification/and look for the Agent Card schema section - Web-search
site:github.com a2aproject A2A agent card schemafor the JSON Schema definition - Web-search
site:github.com a2aproject a2a-samples agent-cardfor real-world Agent Card examples - Fetch SDK docs for Agent Card builder/helper classes
Conceptual Architecture
What the Agent Card Is
The Agent Card is a JSON document that describes an A2A agent to potential clients. It's the discovery and capability advertisement mechanism — analogous to an OpenAPI spec for REST APIs, but for agent-to-agent communication.
Hosting
By convention, Agent Cards are served at:
{agent_base_url}/.well-known/agent-card.json
Agents can also be discovered via:
- Agent registries (centralized directories)
- Direct configuration (hard-coded URLs)
- Referral from other agents
Key Sections
Identity
- name — Human-readable name
- description — What the agent does
- url — The agent's A2A endpoint (where JSON-RPC requests go)
- version — Semantic version of the agent
- protocolVersion — The A2A protocol version the agent supports (required)
- provider — Optional organization/owner information
Capabilities
Declares what protocol features the agent supports:
- streaming — Can the agent handle
message/stream? - pushNotifications — Can the agent send push notifications?
- stateTransitionHistory — Does the agent maintain full task state history?
Skills
Array of skills (capabilities) the agent offers:
- id — Unique skill identifier
- name — Human-readable skill name
- description — What the skill does
- tags — Categorization tags
- examples — Example inputs/prompts for this skill
Skills help client agents understand what tasks they can delegate.
Authentication
Declares required authentication via two top-level fields:
- securitySchemes — A map/object of named security scheme definitions (e.g.,
apiKey,httpwithscheme: bearer,oauth2,openIdConnect) - security — An array of required scheme references (e.g.,
[{ "schemeName": [] }]) - Each scheme has type-specific configuration (header name, OAuth URLs, OIDC discovery URL, etc.)
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 · 96 lines · 42 tokens per session scan A bcccfdaeddc5
a2a-agent-card is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 924 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
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…
lucid-agents
Build, modify, review, debug, or deploy TypeScript services made with the Lucid Agents SDK. Use whenever a project imports @lucid-agents packages or the user asks about Lucid runtimes, entrypoints, adapters, payments, MPP, identity, wallets, A2A tasks, service UI, scaffolding, or deployment.
archestra-dev-rust-napi
Use when editing Rust in this repo — the NAPI crates under platform/archestra-rs (app-runtime, image, and sandbox core/-rs crate pairs plus napi-loader, with their generated TypeScript bindings) or the standalone ai-labs Rust workspace (core/runner/cli/analyzer/dashboard) — including Rust build/test checks.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
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-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.