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/azure/azure-dev/weekly-reportnpx skills add Azure/azure-dev --skill weekly-reportgit clone --depth 1 https://github.com/Azure/azure-devWhat 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.00122 | $0.00772 |
| Opus 5 | $0.00061 | $0.00386 |
| Sonnet 5 | $0.00024 | $0.00154 |
| Haiku 4.5 | $0.00012 | $0.00077 |
Grade A, and why
weekly-report 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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Executive Report Generator
Generates weekly executive reports for the Azure Developer CLI (azd) team leadership.
Prerequisites
| Tool | Purpose |
|---|---|
gh |
GitHub CLI — authenticated with repo access |
jq |
JSON filtering for release queries |
git |
Repository data |
Report Format (strict order)
📝 TLDR
📊 Metrics
⚠️ Risks + Blockers
🎯 Changelog
📋 This Week
🔜 Next Week
🚩 Learnings
🔥 Demos/Links
Execution Flow
Step 1: Confirm date range
Cadence is Thursday to Thursday. Confirm with the user if unclear.
Step 2: Pull repo data
Replace START and END below with the dates from Step 1.
cd <repo-root> # the azure-dev repository root
git checkout main && git pull --rebase
PRs merged:
gh pr list --repo Azure/azure-dev --state merged --search "merged:START..END" --limit 200 --json number,title,mergedAt
Issues closed:
gh issue list --repo Azure/azure-dev --state closed --search "closed:START..END" --limit 200 --json number,title,closedAt
Releases:
gh api repos/Azure/azure-dev/releases --paginate | jq '[.[] | select(.published_at >= "START" and .published_at <= "END") | {name, tag_name, published_at}]'
Step 3: Read changelogs
Changelog data is maintained by the changelog-generation skill.
- Core:
cli/azd/CHANGELOG.md - Agents:
cli/azd/extensions/azure.ai.agents/CHANGELOG.md - Finetuning:
cli/azd/extensions/azure.ai.models/CHANGELOG.md
Step 4: Wait for team notes
Do NOT assemble the report until the user provides team notes from emails, Teams, meetings, etc. Only product and engineering content.
Step 5: Assemble report
Combine repo data with team notes. Follow all rules below.
Step 6: Iterate
Expect 5–15 rounds of edits. Apply changes surgically. After removals, check for related content elsewhere (risks → next week → learnings → TLDR) and offer to clean up.
Output
Save reports to the Copilot CLI session workspace (~/.copilot/session-state/<session-id>/files/) as weekly-report-{month}{startday}-{endday}.md.
What ships with it
2 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.
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.
- 3d ago First seen · 110 lines · 122 tokens per session scan A 43eb7738ab79
weekly-report is a skill published in the GitHub repository Azure/azure-dev (567 stars, last pushed 3d ago), licensed MIT. It adds 122 tokens to every session and 772 once invoked, about $0.0006 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
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.
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)…
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-sdk-mgmt-pr-review
Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.
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.
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…