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 opencue/cuecards --skill agenticx-a2a-connectorgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/agenticx-a2a-connector)<a href="https://agentmods.dev/skills/opencue/cuecards/agenticx-a2a-connector"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/agenticx-a2a-connector/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/opencue/cuecards/agenticx-a2a-connector"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/agenticx-a2a-connector.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.00073 | $0.01195 |
| Opus 5 | $0.00036 | $0.00598 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
agenticx-a2a-connector 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.
This is a copy
100% identical to agenticx-a2a-connector — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticX A2A Connector
Guide for building distributed, inter-communicating agent systems using the A2A protocol.
What is A2A?
A2A (Agent-to-Agent) is a protocol that enables agents to discover each other's capabilities and invoke them as if they were local tools. This allows building distributed agent systems where specialized agents collaborate across network boundaries.
Core Components
| Component | Purpose |
|---|---|
AgentCard |
Advertises an agent's identity and skills |
Skill |
Describes a capability an agent offers |
A2ASkillTool |
Wraps a remote skill as a local tool |
A2ASkillToolFactory |
Batch-creates tools from an AgentCard |
A2AClient |
HTTP client for calling remote agents |
Agent Cards
An AgentCard declares what an agent can do:
from agenticx.protocols import AgentCard, Skill
card = AgentCard(
name="Research Agent",
description="Specializes in web research and report generation",
url="http://research-agent:8000",
skills=[
Skill(
name="web_research",
description="Search the web and compile findings",
parameters_schema={
"type": "object",
"properties": {
"query": {"type": "string"},
"depth": {"type": "integer", "default": 3}
},
"required": ["query"]
}
),
Skill(
name="generate_report",
description="Generate a structured report from research data",
parameters_schema={
"type": "object",
"properties": {
"topic": {"type": "string"},
"format": {"type": "string", "enum": ["markdown", "html"]}
},
"required": ["topic"]
}
)
]
)
Using Remote Agent Skills as Tools
Single Skill
from agenticx.protocols import A2ASkillTool
tool = A2ASkillTool(
agent_url="http://research-agent:8000",
skill_name="web_research"
)
# Use like any local tool
result = tool.run(query="latest AI trends", depth=5)
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 · 174 lines · 73 tokens per session scan A bad5cdef8b81
agenticx-a2a-connector is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,195 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agenticx-a2a-connector, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
api-endpoint
Generate a complete REST API endpoint with validation, tests, and documentation.
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…