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/agents-for-js/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/Agents-for-jsWhat 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.01400 | $0.01400 |
| Opus 5 | $0.00700 | $0.00700 |
| Sonnet 5 | $0.00280 | $0.00280 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
Agents-for-js copilot-instructions.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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot instructions for microsoft/Agents-for-js
The Microsoft 365 Agents SDK for JavaScript/TypeScript (successor to BotFramework SDK v4) — a framework for building agents across M365, Teams, Copilot Studio, and Webchat. It is an npm-workspaces monorepo (packages/* and test-agents/*) using ES modules ("type": "module", module: node16) and TypeScript project references. Requires Node.js 20+ (CI runs Node 24; --env-file requires Node 20.6+).
Commands
npm run build # TypeScript 7 native build via scripts/tsc7.mjs and tsconfig.build.json
npm run build:clean # wipe dist/ then rebuild
npm test # all tests (node:test runner + tsx, emits test-report.xml)
npm run lint # eslint (neostandard config)
npm run lint:deps:ci # knip: unused files/exports/deps must be clean
npm run repo:doctor # repository structure, metadata, docs, and runtime drift
npm run compat # api-extractor public-API compatibility check
npm run build:samples # build the test-agents
Run a single test (the runner is node:test with tsx, not jest/mocha):
node --test --import tsx packages/agents-activity/test/exceptionHelper.test.ts # one file
node --test --import tsx 'packages/agents-hosting/test/**/*.test.ts' # one package
Run npm run repo:doctor after structural, package, documentation, build-reference, dependency, API-baseline, test-agent, Docker, or runtime-configuration changes. Its ESLint-style diagnostics include stable rule IDs and concrete fix instructions for agents and humans.
Do not add npm pre* / post* lifecycle wrappers or install-time hooks (preinstall, install, postinstall, prepare). npm --ignore-scripts skips those hooks; make required script dependencies explicit in the invoked command.
CI (.github/workflows/ci.yml) runs, in order: repo:doctor → lint → lint:deps:ci → build → test → compat → build:samples. Match this before assuming work is done.
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 · 58 lines · 1,400 tokens per session scan A abffa2d55f4c
Agents-for-js copilot-instructions.md is an instructions file published in the GitHub repository microsoft/Agents-for-js (87 stars, last pushed 5d ago), licensed MIT. It adds 1,400 tokens to every session, about $0.0070 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
moss AGENTS.md
Instructions for D-Robotics/moss, covering agents.md, 仓库身份, 文档所有权与阅读顺序, 代码规范执行摘要（必须遵守） and 第一次进入仓库.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
mirage CLAUDE.md
Claude Code instructions for strukto-ai/mirage, covering claude.md, repo layout, typescript packages, python/typescript parity and module layout.
dynatrace-mcp copilot-instructions.md
Instructions for dynatrace-oss/dynatrace-mcp, covering dynatrace mcp server, guidelines, repo structure, coding guidelines and dependencies.
dynatrace-mcp typescript.instructions.md
Instructions for dynatrace-oss/dynatrace-mcp, covering mcp server – typescript agent instructions, reference documentation, project-specific patterns, console.error for logging and implementing mcp tools.
innovation-lab-examples typescript.instructions.md
Instructions for fetchai/innovation-lab-examples, a project described as: 80+ production-ready AI agent examples in Python — build autonomous agents, multi-agent systems and agentic AI with uAgents, ASI:One, MCP, A2A, LangChain, CrewAI, Gemini, Claude and OpenAI.