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 agentmods add skills/microsoft/vscode/chroniclenpx 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.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.06470 |
| Opus 5 | $0.00036 | $0.03235 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 352 lines · 72 tokens per session scan A ff6ba45003d7
chronicle is a skill published in the GitHub repository microsoft/vscode (190,863 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 6,470 once invoked, about $0.0004 per session on Opus 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
nemoclaw-maintainer-release-notes
Drafts the post-tag NemoClaw Announcement from tag, compare, and release-entry data. Use after tagging or when asked to summarize vX.Y.Z.
nemoclaw-maintainer-analyze-pr-value-stream
Analyze one NemoClaw pull request across its complete observable lifetime. Produces a bounded Perfetto trace and summary, separates contributor, review, and automation time, and compares the latest revision with a target. Use for PR latency, value-stream, bottleneck, timeline, or ten-minute-target analysis.
nemoclaw-maintainer-policies
Provide read-only NemoClaw maintainer policy. Use for questions about Issue Type, labels, Project fields, release labels, triage, duplicates, blocked items, and maintainer decisions. Trigger keywords - maintainer policy, workflow policy, project workflow, issue type, labels, label taxonomy, needs labels, project…
agent-browser
Browser automation for testing and verification. Use when you need to interact with web UIs, verify visual changes, fill forms, or capture screenshots.
CreateCLI
Generates production-ready TypeScript CLIs via a 3-tier template system (manual arg parsing, Commander.js, oclif), each shipping full implementation, docs, package.json, strict config, JSON output, and exit-code compliance. USE WHEN create CLI, build CLI, command-line tool, wrap API, add command, upgrade tier…
n8n:create-instance-ai-eval
Authors a new Instance AI workflow eval case — written locally as JSON, calibrated against a real build, then pushed to the LangTracer suite CI runs — build cases, behaviour/process cases, credential cases, and seeded (mid-conversation) cases — with intent-driven expectations. Use when adding or changing an Instance…