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/qa-vault/codelore/migrate-project-docsnpx skills add qa-vault/codelore --skill migrate-project-docsgit clone --depth 1 https://github.com/qa-vault/codeloreWhat 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.00227 | $0.01673 |
| Opus 5 | $0.00113 | $0.00837 |
| Sonnet 5 | $0.00045 | $0.00335 |
| Haiku 4.5 | $0.00023 | $0.00167 |
Grade A, and why
migrate-project-docs 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Project Docs
Bulk-prepares a project's existing markdown documentation for the codelore router
skill (consulting-project-docs) by adding YAML frontmatter to implementation docs and
generating docs/INDEX.md.
The router is useless on day one in a pre-existing project: docs/INDEX.md doesn't
exist and old docs have no frontmatter, so there is nothing to dispatch from. This
skill closes that gap.
When to invoke
- The user explicitly asks: "migrate the docs", "set up codelore docs", "index existing documentation", "add frontmatter to docs".
- The
consulting-project-docsskill detected a missingINDEX.mdand the user agreed to migration. - The
consulting-project-docsskill detected new unfrontmattered docs after a previous migration, and the user agreed to a delta migration.
Do not auto-invoke. The user must agree before any file is touched — this skill modifies many files at once.
Frontmatter contract
Every approved doc gets exactly this block prepended (no other edits to the body):
---
name: <kebab-case identifier, derived from filename without .md>
description: <one-line hook describing the doc, written for AI triage>
---
triggers and related are left unset — the user can fill them in later. See the
document-feature skill for the full schema and field rules.
Workflow
1. Discover candidates
Walk the project's documentation root (docs/ by default; if not present, ask the
user). Collect every .md file under it.
Exclude unconditionally:
docs/INDEX.mditself.- Anything under
docs/plans/,plans/, orspecs/(these are plans, not impl docs). README.mdif it lives atdocs/README.mdand is a navigation index rather than a feature doc — use judgment; if unsure, ask.- Files that already start with a valid YAML frontmatter block containing both
nameanddescription. These are already migrated.
If the resulting candidate list is empty, stop here. Report "nothing to migrate" and exit without touching any file.
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 · 168 lines · 227 tokens per session scan A a2e20a1fe93f
migrate-project-docs is a skill published in the GitHub repository qa-vault/codelore (2 stars, last pushed 4mo ago), licensed MIT. It adds 227 tokens to every session and 1,673 once invoked, about $0.0011 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…