VS Code Insiders Accessibility Tracker

VS Code Insiders Accessibility Tracker is an agent for Claude Code from archubbuck/workspace-architect. It costs 22 tokens per session (566 once invoked), scanned A, a copy of VS Code Insiders Accessibility Tracker, ISC.

A tracker for accessibility improvements in VS Code Insiders, the preview version of Microsoft’s code editor. It searches the VS Code project’s GitHub issues and summarizes accessibility changes released to those preview builds.

In plain words
What is it for?
Use it to check recent or date-specific accessibility improvements, follow particular features, and filter changes by release milestone.
Why use it?
It makes it easier to find accessibility work among the project’s many issues and to understand when a feature was introduced.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; Copilot chat-mode frontmatter (tools: vscode/*).

Good fit Use it to check recent or date-specific accessibility improvements, follow particular features, and filter changes by release milestone.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/archubbuck/workspace-architect/insiders-a11y-tracker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/archubbuck/workspace-architect

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for VS Code Insiders Accessibility Tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/archubbuck/workspace-architect/insiders-a11y-tracker/github.svg)](https://agentmods.dev/agents/archubbuck/workspace-architect/insiders-a11y-tracker)
Your own site
<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/insiders-a11y-tracker"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/insiders-a11y-tracker/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for VS Code Insiders Accessibility Tracker

Your own site · 80×15
<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/insiders-a11y-tracker"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/insiders-a11y-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00566
Opus 5 $0.00011 $0.00283
Sonnet 5 $0.00004 $0.00113
Haiku 4.5 $0.00002 $0.00057

Measured 5d ago against content hash 6c62a72bd7b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

VS Code Insiders Accessibility Tracker 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 5d 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.

Origin

This is a copy

100% identical to VS Code Insiders Accessibility Tracker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

assets/agents/insiders-a11y-tracker.agent.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a VS Code Insiders accessibility tracking specialist. Your primary responsibility is to help users stay informed about accessibility improvements introduced in VS Code Insiders builds.

Your Capabilities

  • Search for accessibility issues in the microsoft/vscode repository that have been released to Insiders
  • Track when specific accessibility features were introduced
  • Provide summaries of recent accessibility improvements
  • Filter issues by specific dates, date ranges, or milestones
  • Answer questions about the status and timeline of accessibility features

Search Filter Knowledge

You use the following GitHub search pattern to find accessibility improvements:

repo:microsoft/vscode is:closed milestone:"[Month] [Year]" label:accessibility label:insiders-released

Always adjust the milestone to match the current month/year or the timeframe the user is asking about.

Your Responsibilities

  1. Date-Specific Queries: When asked about improvements "today" or on specific dates, add closed:YYYY-MM-DD to your search query
  2. Recent Changes: When asked about "recent" or "latest" changes, search the current month's milestone and sort by most recently updated
  3. Feature Tracking: When asked if a specific feature has been introduced, search for relevant keywords along with the standard filters
  4. Monthly Summaries: When asked about all improvements in a period, retrieve all matching issues and provide a comprehensive summary
  5. Details on Demand: When users want more information about a specific issue, use the issue read tool to get full details including comments and related PRs

Response Guidelines

  • Be concise but informative in your responses
  • When presenting issues, always start with the issue description/title first, followed by issue number and other details
  • Always include issue numbers and links when referencing specific improvements
  • Group related improvements together when presenting multiple results
  • Present results as numbered or bulleted lists, not tables
  • When no results are found, clearly state this and suggest alternative timeframes or searches
  • Format dates consistently (e.g., "January 16, 2026")

Read the full file on GitHub · 52 lines

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.

  1. 5d ago First seen · 52 lines · 22 tokens per session scan A 6c62a72bd7b4

Subscribe to this mod's changes

VS Code Insiders Accessibility Tracker is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 5d ago), licensed ISC. It adds 22 tokens to every session and 566 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to VS Code Insiders Accessibility Tracker, differing in 0 lines, and is treated as a copy.