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/microsoft/azure-sql-database-container/azuresql-db-feedbacknpx skills add microsoft/azure-sql-database-container --skill azuresql-db-feedbackgit clone --depth 1 https://github.com/microsoft/azure-sql-database-containerWhat 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.00204 | $0.01974 |
| Opus 5 | $0.00102 | $0.00987 |
| Sonnet 5 | $0.00041 | $0.00395 |
| Haiku 4.5 | $0.00020 | $0.00197 |
Grade A, and why
azuresql-db-feedback 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report a problem with the skills, or with the container
The user should never have to assemble a bug report by hand. You are already holding what a good one needs: which skill you were following, what it told you to do, what you actually had to do, the image tag, the host, the runtime, the failing command, and the error. Your job is to turn that into a complete report and hand it to the user to submit.
Repository: microsoft/azure-sql-database-container (both the container and the skills live here).
The two rules that matter most
- Never create an issue without explicit confirmation. Show the user the full title and body first and
wait for a clear yes. You may offer; you may never submit unasked. This applies to every path below,
including the
ghCLI. - Redact before you send. Everything submitted is public. See Redaction.
Step 1: skill problem, or container problem?
Get this right first: they use different issue templates.
Ask yourself what actually failed.
| The problem | It belongs to | Template |
|---|---|---|
| A skill told the agent to do the wrong thing, or failed to say something it needed to say | the skill | skill_feedback.yml |
| The wrong skill loaded, or no skill loaded when one should have | the skill | skill_feedback.yml |
| A skill would not install, or the agent never picked it up | the skill | skill_feedback.yml |
| You had to deviate from the skill or work around it to make the task succeed | the skill | skill_feedback.yml |
| The skill said the right thing, the agent did the right thing, and the container still failed (will not start, query errors, engine behaves unexpectedly) | the container | bug_report.yml |
| The container is missing a capability the user wants | the container | feature_request.yml |
The test that settles it: if the instructions were correct and the engine still broke, it is a container bug. If the instructions were wrong, incomplete, or ignored, it is a skill bug. When genuinely torn, ask the user. Do not guess, and do not file both.
What ships with it
1 file 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.
- 2d ago First seen · 124 lines · 204 tokens per session scan A b96e6fcd0d18
azuresql-db-feedback is a skill published in the GitHub repository microsoft/azure-sql-database-container (16 stars, last pushed yesterday), licensed MIT. It adds 204 tokens to every session and 1,974 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.