agentmods.dev

create-package-skill

An interactive wizard for creating a package-specific instruction guide for an Azure SDK package. It scans the package, creates a SKILL.md file with references, and checks it with a linter.

In plain words
What is it for?
Use it to inspect an Azure SDK package, identify its custom patterns, scaffold its skill file, and validate the result in the package’s .github/skills/ directory.
Why use it?
It helps teams capture package knowledge that is not obvious from the source code. It also gives the guide a consistent structure and checks it before use.

Skill for Claude CodeCodex

2.6k +1 today A scan 106 tokens original MIT
View the source file Azure/azure-sdk-for-java
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.

agentmods
npx agentmods add skills/azure/azure-sdk-for-java/create-package-skill
Any agent
npx skills add Azure/azure-sdk-for-java --skill create-package-skill
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-sdk-for-java

Made for: Claude Code, Codex.

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,041 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00106 $0.01041
Opus 5 $0.00053 $0.00521
Sonnet 5 $0.00021 $0.00208
Haiku 4.5 $0.00011 $0.00104

Measured 2d ago against content hash 39b6ac579529, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-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 2d 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.

.github/skills/create-package-skill/SKILL.md · 77 lines

How it starts

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

Create Package Skill Wizard

Minimal beats comprehensive. Human-written beats auto-generated. Scaffold and iterate.

Skills encode tribal knowledge — the "I wish someone had told me" stuff that's hard to learn from just reading code. Focus on what's non-obvious and package-specific.

Interaction Protocols

CONFIRM Protocol (asset-producing steps — creating files):

  1. PRESENT the proposed assets and explain why.
  2. ASK exactly one question: "Create now (recommended), edit first, or skip?"
  3. ACT immediately. Create → write files this turn. Edit → refine, re-ask. Skip → move on.

DECIDE Protocol (informational/correction steps — no files created):

  1. PRESENT the information or findings.
  2. ASK one specific question appropriate to the decision.
  3. PROCEED based on the answer.

One question at a time. Respect "skip" — never re-ask or defer.

Wizard Flow

Run each phase in order. Progressive loading: Read only the current phase file.

Phase Description Instructions
Phase 0 🧭 Scan Package — detect architecture, customizations, key files phases/00-scan-package.md
Phase 1 📝 Scaffold SKILL.md — generate skill with common pitfalls, architecture, workflow phases/01-scaffold-skill.md
Phase 2 📚 Generate References — create architecture.md and customizations.md phases/02-generate-references.md
Phase 3 Validate -- run vally lint phases/03-validate.md
Phase 4 📋 Finalize — confirm discoverable location, summarize phases/04-finalize.md

Guardrails

Content:

  • Every line must be non-obvious and package-specific. No generic Java/SDK patterns.
  • SKILL.md should be under 500 tokens (soft limit). Move details to references/.
  • References under 1000 tokens each. Split if larger.
  • Never duplicate what's already in .github/copilot-instructions.md or shared skills.

Read the full file on GitHub · 77 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 77 lines · 106 tokens per session scan A 39b6ac579529

Subscribe to this mod's changes

create-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 106 tokens to every session and 1,041 once invoked, about $0.0005 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.

Building agentsazureazure-resourcesazure-sdkazure-servicesmedia
Related

Other skills, from other repositories

dpg-migration

Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.

Azure/azure-sdk-for-net · 41 tokens

csharp-azure-spector-coverage-gaps

Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…

Azure/azure-sdk-for-net · 78 tokens

auto-build-repair

Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…

Azure/azure-sdk-for-net · 149 tokens

azure-sdk-mgmt-pr-review

Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.

Azure/azure-sdk-for-net · 26 tokens

mgmt-review-comment-resolution

Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.

Azure/azure-sdk-for-net · 46 tokens

mitigate-breaking-changes

Patterns and techniques for mitigating breaking changes during Azure management-plane SDK migration from Swagger/AutoRest to TypeSpec. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType…

Azure/azure-sdk-for-net · 68 tokens