Azure SDK for Java is a collection of Java libraries that let applications connect to and manage Azure services. Java developers use its client libraries to consume services and its management libraries to configure Azure resources. The catalogue add-ons support development with these libraries.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-java. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-java/main/.github/skills/find-package-skill/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-javaWrote 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/azure/azure-sdk-for-java/find-package-skill)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-java/find-package-skill"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-java/find-package-skill/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/azure/azure-sdk-for-java/find-package-skill"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-java/find-package-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.00388 |
| Opus 5.5 | $0.00024 | $0.00155 |
| Sonnet 5.5 | $0.00012 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
find-package-skill 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.
What it actually says
Find Package Skill
Some SDK packages in this monorepo have package-specific skills — tribal knowledge (architecture, data flows, type mappings, pitfalls) that prevents common mistakes. Before modifying any SDK package, check whether a skill exists for it using the steps below.
How to Discover Package Skills
-
Determine the package directory. If you already know the file path you're modifying, extract the package directory from it (e.g., a file at
sdk/search/azure-search-documents/src/main/java/com/azure/search/documents/SearchClient.javabelongs to the package atsdk/search/azure-search-documents/). If you only have a package name, search for a matching directory undersdk/(package directories are named after the Maven artifactId, e.g.,com.azure:azure-search-documents→sdk/search/azure-search-documents/). -
Check for a
.github/skills/directory inside the package directory. For example, check whethersdk/search/azure-search-documents/.github/skills/exists. -
If it exists, read every
SKILL.mdfound under that directory. If areferences/subdirectory exists next to aSKILL.md, read all files in it too for additional context. -
If no
.github/skills/directory exists for the package, no package-specific skill has been created yet — proceed normally.
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.
- 1mo ago First seen · 32 lines · 61 tokens per session scan A 735319a23af4
find-package-skill is a skill published in the GitHub repository Azure/azure-sdk-for-java (2,565 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 388 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.
Other skills, from other repositories
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
tika-eval-encoding-regression
Condensed tika-eval pattern for charset-detector regression hunts ("A picks encoding X, B picks Y") using one build and two configs — encoding-pair flip queries, OOV/languageness/FFFD signals, per-file detector attribution.
azure-monitor-query-java
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources. Triggers: "LogsQueryClient java", "MetricsQueryClient java", "kusto query java", "log analytics java", "azure monitor query java". Note: This package is deprecated. Migrate to…
wxjava-troubleshooter
A troubleshooting guide for WxJava, a Java library used to connect applications to WeChat services. It organizes problems involving setup, access tokens, signatures, payment certificates, callbacks, data conversion, network requests, and multiple accounts.