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 agents/kimiski33/awesome-copilot/code-tourgit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWhat 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.00023 | $0.01600 |
| Opus 5 | $0.00012 | $0.00800 |
| Sonnet 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 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.
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.
- 2d ago First seen · 206 lines · 23 tokens per session scan A 99c7b870acb8
VSCode Tour Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. 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.
Other agents, from other repositories
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
code-explainer
Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
technical-evaluator
프론트엔드 기술 역량 평가 전문가. 면접 질문지와 답변을 기반으로 기술적 역량을 엄격하게 평가합니다. /evaluate 커맨드에서 자동 호출됩니다.
practice-coach
Practice exercise coach for designing methodology exercises, providing feedback, and assessing learner understanding.
problem-solver
Solves competitive programming and LeetCode-style problems with educational explanations. Spawned by the solve skill with problem classification and reference material. Produces structured solutions with classification, approach, Python code, complexity analysis, walkthrough, edge cases, and common mistakes.