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/vscode/accessibilitygit clone --depth 1 https://github.com/microsoft/vscodeWhat 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.00611 | $0.00611 |
| Opus 5 | $0.00305 | $0.00305 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
vscode accessibility.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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- nyrve accessibility.instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Guidelines
Accessibility is a high-priority area in VS Code. Follow these patterns to ensure features work correctly with screen readers and assistive technologies.
Keybinding Scoping
Accessibility-specific keybindings MUST be scoped to prevent conflicts with standard shortcuts:
keybinding: {
primary: KeyCode.F7,
when: ContextKeyExpr.and(
EditorContextKeys.focus,
CONTEXT_ACCESSIBILITY_MODE_ENABLED
),
weight: KeybindingWeight.WorkbenchContrib,
},
Why: Without scoping, accessibility shortcuts steal commonly used keybindings (e.g., F7 for "Go to Next Symbol Highlight"). PR #293163 fixed this exact conflict.
Accessible Help Dialogs (Alt+F1)
Use AccessibleContentProvider directly — do not create custom subclasses:
getProvider(): AccessibleContentProvider {
return new AccessibleContentProvider(
AccessibleViewProviderId.MyFeature,
{ type: AccessibleViewType.Help },
() => this.getHelpContent(),
() => this.onClose(),
'accessibility.verbosity.myFeature'
);
}
Announcement Patterns
When announcing state changes to screen readers:
- Only announce when conditions are met: Check that a search string is present, widget is visible, and screen reader is active
- Prevent double-speak: Track announcement state with a flag and use a timeout (~1 second)
- Use verbosity settings: Check
accessibility.verbosity.[feature]before verbose announcements
if (this.accessibilityService.isScreenReaderOptimized() &&
this.configService.getValue('accessibility.verbosity.hover') &&
!this._accessibilityHelpHintAnnounced) {
this._accessibilityHelpHintAnnounced = true;
// announce hint
}
Multi-Modal Notifications
For important state changes, provide all three:
- Audio signal:
this.accessibilitySignalService.playSignal(AccessibilitySignal.chatUserActionRequired) - ARIA alert:
status(message)for screen readers - OS notification: Respect
chat.notifyWindowOnConfirmationsetting. OS notifications are conditional on window focus — only fire whentargetWindow.document.hasFocus()isfalse(seeChatWindowNotifier)
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.
- yesterday First seen · 80 lines · 611 tokens per session scan A ecfa3dd0d6f6
vscode accessibility.instructions.md is an instructions file published in the GitHub repository microsoft/vscode (190,061 stars, last pushed yesterday), licensed MIT. It adds 611 tokens to every session, about $0.0031 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
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
vscode-peacock copilot-instructions.md
Instructions for johnpapa/vscode-peacock, covering copilot instructions — peacock, project type, typescript conventions, vs code extension patterns and color handling.
code-by-wire CLAUDE.md
Instructions for luojiahai/code-by-wire, covering claude.md, development, website, architecture and code style.
swob AGENTS.md
Instructions for IvyYang1999/swob, covering swob 研发协作唯一规范, 不可越过的边界, 角色与职责, 生命周期 and 分支、worktree 与提交.
clodex-ide AGENTS.md
AGENTS.md instructions for mereyabdenbekuly-ctrl/clodex-ide, covering clodex repository agent rules, open/closed product boundary, commercial product invariant, current protocol v0 phase and current authorization state.
data-peek CLAUDE.md
Claude Code instructions for Rohithgilla12/data-peek, covering claude.md, project overview, commands, development (from root) and from apps/desktop.