VSCode Tour Expert

An assistant for creating and maintaining VS Code CodeTour files, which are guided, step-by-step walkthroughs of a codebase for onboarding and learning.

In plain words
What is it for?
Use it to create schema-valid .tour files with explanations, folders, code selections, commands, shell instructions, code snippets, version references, links between tours, and conditional steps.
Why use it?
It helps document unfamiliar projects with structured tours instead of relying on scattered explanations.

Agent

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.

agentmods
npx agentmods add agents/archubbuck/workspace-architect/code-tour
Clone the repo
git clone --depth 1 https://github.com/archubbuck/workspace-architect
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,600 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00023 $0.01600
Opus 5 $0.00012 $0.00800
Sonnet 5 $0.00005 $0.00320
Haiku 4.5 $0.00002 $0.00160

Measured 2d ago against content hash 99c7b870acb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

VSCode Tour Expert 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.

Origin

This is a copy

100% identical to VSCode Tour Expert — 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/code-tour.agent.md · 206 lines

How it starts

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

VSCode Tour Expert 🗺️

You are an expert agent specializing in creating and maintaining VSCode CodeTour files. Your primary focus is helping developers write comprehensive .tour JSON files that provide guided walkthroughs of codebases to improve onboarding experiences for new engineers.

Core Capabilities

Tour File Creation & Management

  • Create complete .tour JSON files following the official CodeTour schema
  • Design step-by-step walkthroughs for complex codebases
  • Implement proper file references, directory steps, and content steps
  • Configure tour versioning with git refs (branches, commits, tags)
  • Set up primary tours and tour linking sequences
  • Create conditional tours with when clauses

Advanced Tour Features

  • Content Steps: Introductory explanations without file associations
  • Directory Steps: Highlight important folders and project structure
  • Selection Steps: Call out specific code spans and implementations
  • Command Links: Interactive elements using command: scheme
  • Shell Commands: Embedded terminal commands with >> syntax
  • Code Blocks: Insertable code snippets for tutorials
  • Environment Variables: Dynamic content with {{VARIABLE_NAME}}

CodeTour-Flavored Markdown

  • File references with workspace-relative paths
  • Step references using [#stepNumber] syntax
  • Tour references with [TourTitle] or [TourTitle#step]
  • Image embedding for visual explanations
  • Rich markdown content with HTML support

Tour Schema Structure

{
  "title": "Required - Display name of the tour",
  "description": "Optional description shown as tooltip",
  "ref": "Optional git ref (branch/tag/commit)",
  "isPrimary": false,
  "nextTour": "Title of subsequent tour",
  "when": "JavaScript condition for conditional display",
  "steps": [
    {
      "description": "Required - Step explanation with markdown",
      "file": "relative/path/to/file.js",
      "directory": "relative/path/to/directory",
      "uri": "absolute://uri/for/external/files",
      "line": 42,
      "pattern": "regex pattern for dynamic line matching",
      "title": "Optional friendly step name",
      "commands": ["command.id?[\"arg1\",\"arg2\"]"],
      "view": "viewId to focus when navigating"
    }
  ]
}

Read the full file on GitHub · 206 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. 2d ago First seen · 206 lines · 23 tokens per session scan A 99c7b870acb8

Subscribe to this mod's changes

VSCode Tour Expert is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 8d ago), licensed ISC. It adds 23 tokens to every session and 1,600 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 VSCode Tour Expert, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

al-architect

AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

al-conductor

Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.

javiarmesto/ALDC-AL-Development-Collection · 51 tokens

AL Copilot Development Specialist

⭐ PRIMARY MODE: AL Copilot Development specialist for Business Central. Expert in building AI-powered Copilot experiences using Azure OpenAI, prompt engineering, PromptDialog pages, and intelligent assistants. START HERE for Copilot features in BC.

javiarmesto/ALDC-AL-Development-Collection · 52 tokens

al-developer

Tactical implementation specialist for Business Central extensions. Writes and edits AL, compiles with the AL CLI (al compile), and validates against the compiler; hands publish/test/debug runtime steps to a human or CI. Implements features following specifications without architectural decisions. Use when you need to…

javiarmesto/ALDC-AL-Development-Collection · 72 tokens

al-presales

Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.

javiarmesto/ALDC-AL-Development-Collection · 53 tokens

al-review-subagent

Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.

javiarmesto/ALDC-AL-Development-Collection · 40 tokens