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.
git clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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.
[](https://agentmods.dev/agents/archubbuck/workspace-architect/code-tour)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/code-tour"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/code-tour/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.
<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/code-tour"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/code-tour.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00023 | $0.01600 |
| Opus 5.5 | $0.00009 | $0.00640 |
| Sonnet 5.5 | $0.00005 | $0.00320 |
| Haiku 4.5 | $0.00002 | $0.00160 |
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 1mo 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.
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.
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
.tourJSON 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
whenclauses
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"
}
]
}
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.
- 1mo ago First seen · 206 lines · 23 tokens per session scan A 99c7b870acb8
VSCode Tour Expert is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 2d ago), licensed ISC. It adds 23 tokens to every session and 1,600 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
bitlesson-selector
Selects required BitLesson entries for a specific sub-task. Use before execution for every task or sub-task.
course-planner
Plans a full course outline (chat-first) and prepares metadata and lesson scaffolding guidance. Use when the user asks to design a course.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.