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/agent365-skills/a365-code-validatornpx skills add microsoft/agent365-skills --skill a365-code-validatorgit clone --depth 1 https://github.com/microsoft/agent365-skillsWhat 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.00194 | $0.05567 |
| Opus 5 | $0.00097 | $0.02783 |
| Sonnet 5 | $0.00039 | $0.01113 |
| Haiku 4.5 | $0.00019 | $0.00557 |
Grade A, and why
a365-code-validator 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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A365 Code Validator
Trigger phrases — any of these will activate this skill automatically:
- "validate a365 code"
- "run a365 code validator"
- "check a365 observability code"
- "debug a365 activity missing"
- "debug MAC activity for this agent"
- "validate Agent 365 telemetry"
- "check why Agent Activity is empty"
- "check A365 exporter flags"
- "validate gen_ai agent id"
- "check A365 span types"
Overview
This skill performs a report-first validation of an existing agent codebase to answer:
"If this agent runs now, will its spans reach the A365 backend and become eligible for MAC Activity?"
It is designed for incident response. It checks the exact classes of bugs that cause silent or confusing A365 Activity failures:
- Exporter configured but not actually enabled.
gen_ai.agent.idset to a Blueprint ID instead of the runtime Agent Identity / Source Agent ID.- Generic HTTP/OpenAI spans emitted without A365 semantic operations.
- S2S/OBO endpoint mismatch.
- Missing token resolver or wrong S2S token shape.
- Stale local Blueprint ID or missing Blueprint permissions in the target tenant.
- Inheritable permission policy configured without grants on the Blueprint service principal.
- MAC reporting expectations confused with raw ingest success.
No source code is modified during validation. After the report, the skill asks whether to apply safe fixes, create a fix plan only, or stop.
Output is support-safe (applies to every phase)
This report may be pasted into a customer or partner thread, so it must be safe to share: never print internal cluster/database names, Kusto queries, private endpoint or route templates, correlation IDs, or real tenant/agent IDs. Report file/function names and public, supportable signals only. This is non-negotiable — it holds even when a user asks for "just the raw details."
Phase 0 — Create and Display Task List
Show the user this checklist BEFORE Phase 1. Exactly one task is in progress at a time. Claude Code uses
TaskCreate/TaskUpdate; VS Code Copilot Chat / GitHub Copilot CLI should show and update a markdown checklist.
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 · 632 lines · 194 tokens per session scan A e747930a4b52
a365-code-validator is a skill published in the GitHub repository microsoft/agent365-skills (32 stars, last pushed 7d ago), licensed MIT. It adds 194 tokens to every session and 5,567 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…