Visual Studio Code is a code editor that supports editing, navigating, understanding, debugging, and extending software projects. Developers use it for the edit-build-debug cycle, and the catalogue add-ons provide skills, instructions, and agents for working within the editor.
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 skills add microsoft/vscode --skill chroniclegit clone --depth 1 https://github.com/microsoft/vscodeWrote 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/skills/microsoft/vscode/chronicle)<a href="https://agentmods.dev/skills/microsoft/vscode/chronicle"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/chronicle/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/skills/microsoft/vscode/chronicle"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/chronicle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00072 | $0.06470 |
| Opus 5.5 | $0.00029 | $0.02588 |
| Sonnet 5.5 | $0.00014 | $0.01294 |
| Haiku 4.5 | $0.00007 | $0.00647 |
Grade A, and why
chronicle 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.
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle
Analyze the user's Copilot session history using the copilot_sessionStoreSql tool. This skill handles standup reports, usage analysis, session search, and session store maintenance.
Sessions may be stored locally (SQLite) and optionally synced to the cloud for cross-device access. Cloud sync is controlled by the chat.sessionSync.enabled setting.
Prerequisite: Chronicle requires the github.copilot.chat.localIndex.enabled setting to be true. If the copilot_sessionStoreSql tool is not available, tell the user to enable this setting in VS Code Settings.
Available Tool Actions
The copilot_sessionStoreSql tool supports two actions:
| Action | Purpose | query param |
|---|---|---|
query |
Execute a read-only SQL query | Required |
reindex |
Rebuild local session index + cloud sync | Not needed |
Workflows
Standup
When the user asks for a standup, daily summary, or "what did I do" (e.g. /chronicle standup):
Step 1: Gather the last 24h of activity
Use copilot_sessionStoreSql with action: "query" and follow the SQL dialect shown in the tool description (SQLite locally, DuckDB on cloud — see the Database Schema and Query Guidelines sections below).
Query the sessions table for rows where updated_at falls within the last 24 hours, ordered by updated_at descending. Recent-window predicate by backend:
- Local SQLite:
WHERE updated_at >= datetime('now', '-1 day') - Cloud DuckDB:
WHERE updated_at >= now() - INTERVAL '1 day'
Then, for those session ids, pull related references from session_refs (PRs, issues, commits). If you need more detail on a particular session, query turns (and session_files, or checkpoints on cloud) further — don't dump every turn for every session up front.
If no sessions are found in the last 24 hours, tell the user there's no recent activity to report, suggest a longer window or /chronicle reindex, and stop. Do not fabricate a standup.
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 · 352 lines · 72 tokens per session scan A ff6ba45003d7
chronicle is a skill published in the GitHub repository microsoft/vscode (193,981 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 6,470 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and workflowbuildercreatetasks silence rules. Load whenever any of these tags appear or after calling workflowbuildercreatetasks.
om-build-workflow
Build or extend standalone business workflows, activities, event triggers, durable user tasks, compensation, output paths, idempotency, and live progress. Use for "add workflow", "custom activity", "CALLAPI", "approval task", "workflow progress", or "zbuduj workflow".
output-eval-error-analysis
Systematically review workflow traces to identify failure modes before building evaluators. Use when starting an eval project, after significant pipeline changes, or when production quality drops.
output-dev-code-style
Code style conventions for Output SDK workflow projects. Use when writing or reviewing any TypeScript/JavaScript code. Discovers the project's own linting rules first; falls back to Output SDK conventions when no linter is configured.
output-dev-llm-streaming
Implement LLM text streaming in Output workflow steps with generateTextWithStreaming, Agent.generateWithStreaming, streamText, or Agent.stream. Use when adding token progress, onChunk callbacks, or handling streamText onEnd/onError with Temporal retries.
output-dev-workflow-cost
Calculate and display the cost of an Output SDK workflow execution run. Use when checking LLM token costs, API service costs, or total spend for a specific workflow run.