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/drvoss/everything-copilot-cli/knowledge-curatornpx skills add drvoss/everything-copilot-cli --skill knowledge-curatorgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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.00038 | $0.01263 |
| Opus 5 | $0.00019 | $0.00632 |
| Sonnet 5 | $0.00008 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
knowledge-curator 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Curator
Not every useful insight belongs in a one-off chat. Knowledge Curator turns repeated lessons from session history into maintainable project guidance so future sessions start from better defaults.
Why This is Copilot-Exclusive
Copilot CLI gives you three building blocks that work well together:
- Session artifacts for saving structured notes during a task
/resumefor continuing a past session with its artifacts and SQL statesession_storesearch for finding prior discussions and patterns later
The key constraint matters: session_store is read-only historical memory, not a writable
knowledge base. This skill is about deciding what should graduate from temporary session context
into durable project docs such as .github/copilot-instructions.md, CONTRIBUTING.md, or
reference guides.
When to Use
- The same repo-specific warning or pattern keeps appearing across sessions
- A temporary workaround has become a stable team practice
- You want to prune stale guidance instead of accumulating contradictory notes
- A sprint or migration produced lessons worth promoting into project instructions
When NOT to Use
| Instead of knowledge-curator | Use |
|---|---|
| You only need to find something from a past session | copilot-exclusive/cross-session-memory |
| You need a first-pass backlog from external ecosystem research | copilot-exclusive/ecosystem-intake |
| You are documenting a single hard-to-reverse technical decision | documentation/architecture-decisions |
Prerequisites
- A candidate insight worth keeping
- A target destination for that insight
- Enough evidence to tell whether it is stable, repeated, or obsolete
Knowledge Layers
| Layer | Medium | Best for |
|---|---|---|
| Session | session artifacts, SQL notes, current plan | In-progress findings, experiments, temporary context |
| Historical | session_store search + /resume |
Looking up what happened in earlier sessions |
| Durable | .github/copilot-instructions.md, CONTRIBUTING.md, reference docs |
Stable project rules, patterns, and team-facing guidance |
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 · 167 lines · 38 tokens per session scan A c385935f5285
knowledge-curator is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,263 once invoked, about $0.0002 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-30.
Other skills, from other repositories
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
journey-template
Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App Service). USE FOR: new journey, scaffold…