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 instructions/microsoft/build-cli/agents-mdgit clone --depth 1 https://github.com/microsoft/Build-CLIWhat 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.00946 | $0.00946 |
| Opus 5 | $0.00473 | $0.00473 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
Build-CLI AGENTS.md 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repo packages the Microsoft Events assistant plugin and the @microsoft/events-cli CLI. The plugin helps agents use live Microsoft Build and Ignite session catalogs; the CLI fetches, caches, normalizes, and searches those catalogs.
Plugin ecosystems
The repo publishes plugin metadata for GitHub Copilot and Claude Code. Keep shared product identity fields aligned across the manifests when changing the plugin name, description, version, author, repository, keywords, license, skills path, or MCP wiring.
Shared assets used by the plugin ecosystems:
skills\microsoft-build\SKILL.md— the active skill prompt.mcp.json— Microsoft Learn MCP endpoint configcli\— source for the@microsoft/events-clipackage used by the skill
Versioned plugin manifests:
- GitHub Copilot —
.github\plugin\plugin.jsonis the Copilot marketplace manifest and points at the repo root. - Claude Code —
.claude-plugin\plugin.jsondefines the Claude Code plugin package;.claude-plugin\marketplace.jsondefines Claude Code marketplace publishing metadata.
Sync rules
- Event support is duplicated by design between the CLI and skill docs. When adding, removing, or renaming events, update
cli\src\config.ts, the supported/default event guidance inskills\microsoft-build\SKILL.md, and affected tests/docs together. - Treat
skills\microsoft-build\SKILL.mdas the product contract for event-session behavior. For Build, Ignite, or event-session work: default "Build" tobuild-2026, get session metadata from the live catalog throughmseventsor the endpoint, get SDK/API facts from Microsoft Learn MCP, and never invent session IDs, speakers, schedules, or links. - Versioning gate: any meaningful
skills\microsoft-build\SKILL.mdchange (agent behavior, commands/examples agents may follow, supported/default events, CLI/MCP/catalog usage, or user-facing workflow guidance) must bump both versioned plugin manifests to the same value; patch bumps are fine for guidance-only changes. - PR review gate: GitHub Copilot/code reviewers should flag meaningful
SKILL.mdchanges without synced plugin version bumps, and any plugin version drift. Typo/format-only skill edits may skip the bump only when the PR explicitly says so. - Keep README install/client guidance aligned with plugin manifest, skill, MCP, or CLI behavior 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.
- 2d ago First seen · 55 lines · 946 tokens per session scan A b6e29c43c642
Build-CLI AGENTS.md is an instructions file published in the GitHub repository microsoft/Build-CLI (294 stars, last pushed 4d ago), licensed MIT. It adds 946 tokens to every session, about $0.0047 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 instructions, from other repositories
spec-kit-copilot AGENTS.md
Instructions for github/spec-kit-copilot, covering what this repository is, core skills plugin, core decisions (do not silently undo) and when revving the core skills plugin.
sts2-llm copilot-instructions.md
Instructions for ttxttx1111/sts2-llm, covering copilot instructions for this repository, source of truth for customizations, runtime assumptions, authoring rules for this repo and gameplay-specific expectations.
sts2-llm skills.instructions.md
Instructions for ttxttx1111/sts2-llm, covering skill 文件与变更记录说明, 基本规则, 修改 skill 时的最小要求, 何时要同步更新总文档 and 工作方式.
sts2-llm runtime.instructions.md
Instructions for ttxttx1111/sts2-llm, a project described as: GitHub Copilot player agent customization pack for Slay the Spire 2 via STS2MCP.
sts2-llm live-data.instructions.md
Instructions for ttxttx1111/sts2-llm, a project described as: GitHub Copilot player agent customization pack for Slay the Spire 2 via STS2MCP.
groundhog-day AGENTS.md
Instructions for DUBSOpenHub/groundhog-day, covering agents.md: working guide for ai agents, architecture, file ownership map, key design decisions and 1. no external dependencies beyond standard tools.