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 agentmods add skills/a2aproject/a2a-java/release-a2anpx skills add a2aproject/a2a-java --skill release-a2agit clone --depth 1 https://github.com/a2aproject/a2a-javaWhat 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 | $0.00036 | $0.02462 |
| Opus 5 | $0.00018 | $0.01231 |
| Sonnet 5 | $0.00007 | $0.00492 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade A, and why
release-a2a 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 yesterday.
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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process
Guide the full release lifecycle. Proceed autonomously through mechanical steps (running scripts, polling CI, creating PRs) and pause only for genuine decisions, failures, or destructive actions.
Phase 0: Determine Release Parameters
-
Read the current version from the root
pom.xml— the-SNAPSHOTsuffix indicates the current dev version. -
Ask the user which version to release if not already specified.
-
Apply the Final suffix convention: if the user specifies a plain version like
1.2.0, the release version is1.2.0.Final. Pre-release qualifiers (Alpha1,Beta1,CR1) are used as-is. -
Suggest a sensible next SNAPSHOT version and confirm with the user:
- Final:
1.1.0.Final→1.1.1.Final-SNAPSHOT - Pre-release:
1.1.0.Alpha1→1.1.0.Alpha2-SNAPSHOT
- Final:
-
Determine the documentation plan:
- Skip for micro/patch releases (X.Y.Z where Z > 0)
- Ask for pre-releases (Alpha/Beta/CR)
- Yes for major/minor Final releases (X.Y.0.Final)
-
Detect git remotes. Run
git remote -vand identify:- Upstream remote: the remote whose URL contains
a2aproject/a2a-java(this is the canonical repo — it may be calledupstream,origin, or anything else). - Fork remote: a different remote owned by the current user (typically
origin). Extract the fork owner from its URL (e.g.,kabirfromgithub.com:kabir/a2a-java.git).
Throughout this skill,
<upstream>refers to the detected upstream remote name and<fork>refers to the fork remote name. All PRs are created from the fork, and tags/main are pushed to/pulled from upstream. - Upstream remote: the remote whose URL contains
Phase 1: Pre-Release Verification
-
Verify
ghCLI is installed and authenticated:gh auth statusIf not installed or not logged in, stop and ask the user to run
gh auth login. -
Verify clean working tree:
git statusIf there are uncommitted changes, stop and ask.
-
Verify we are on
mainand in sync with upstream. Fetch first to ensure the remote ref is current:git fetch <upstream> main git log --oneline HEAD..<upstream>/main git log --oneline <upstream>/main..HEADIf local main is behind or ahead of
<upstream>/main, stop and ask the user.
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.
- yesterday First seen · 230 lines · 36 tokens per session scan A e5de10c9d339
release-a2a is a skill published in the GitHub repository a2aproject/a2a-java (481 stars, last pushed 4d ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,462 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
frankfurter
Fetch currency exchange rates from the frankfurter.dev API.
a2a-adapter
Use when building A2A Protocol agents, converting AI agents from any framework (LangChain, CrewAI, n8n, LangGraph, Ollama, or custom) into A2A-compatible servers, or working with the a2a-adapter Python SDK.
check_date
Check the current date through a local system tool.
mistake-reflection
Use when you discover you made a mistake — caught by the user, by a tool result, by your own re-reading, or by a failed check. Appends a structured entry to docs/ai/ailearnings.md and re-reads recent entries to avoid repeats.
searxng-settings-editor
Inspect and edit the EMBEDDED SearXNG instance's settings.yml (the private, loopback-only, zero-config search fallback the searxng-mcp server can own end to end when no external SEARXNGURL is configured). Use when the agent or operator wants to change what the embedded instance does — enable/ disable formats, flip…
searxng-kg-ingestion
Persist SearXNG search results into the epistemic-graph knowledge graph via the searxng-mcp MCP server. Use when the agent must turn a web search into durable, semantically-searchable KG memory — each result becomes a :Document (plus :SearchQuery and :SearchEngine typed nodes with :resultOf / :fromEngine links) so…