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/buildrai/buildr/current-knowledge-maintenancenpx skills add BuildrAI/Buildr --skill current-knowledge-maintenancegit clone --depth 1 https://github.com/BuildrAI/BuildrWrote 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/buildrai/buildr/current-knowledge-maintenance)<a href="https://agentmods.dev/skills/buildrai/buildr/current-knowledge-maintenance"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/current-knowledge-maintenance.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.00071 | $0.01718 |
| Opus 5 | $0.00036 | $0.00859 |
| Sonnet 5 | $0.00014 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
Grade A, and why
current-knowledge-maintenance 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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
当前认知维护
本 Skill 同时是 buildr.current-knowledge-maintenance/v1 与 v2 的默认 provider，并 required 依赖 buildr.terminology-governance/v1。v1 保持 Change lifecycle 的 assess、reconcile、inspect；v2 另外支持不依附 Change 的 maintain，让已确认当前事实进入人类可读当前认知。
1. 解析 operation 与事实范围
读取 runtime binding 中与 operation 匹配的 contract 和 selected terminology provider，解析 Workspace、Project、当前 tree identity 与授权范围。Change lifecycle operations 另外解析 Change、artifact paths 与已有 .buildr/knowledge-impact.yml。只接受：
assess：proposal/update 阶段评估影响；reconcile：实现完成、最终验证前收敛内容；inspect：针对current tree在实现、Review或Verification前后形成完成影响分类，不把检查冒充验证execution；maintain：没有 Change 时，让 current knowledge 追上已由权威来源确认的既有事实。
事实顺序是 canonical specs → 当前实现与 registries → active Change artifacts → 已确认 evidence/用户决定 → archive provenance。冲突时先修正权威资产，再更新解释性 knowledge。
2. 按真实影响选择目标
| 目标 | 触发事实 |
|---|---|
brief.md |
每个正式 Change；scope、流程、影响或验收变化 |
overview.md |
Project 定位、用户、核心能力或全局入口 |
architecture/product.md |
角色、业务能力、领域模块、产品边界或信息架构 |
architecture/technical.md |
Service 拓扑、模块边界、数据所有权、接口依赖、runtime、部署或安全 |
flows/<flow-id>.md |
用户旅程、业务状态、跨模块/Service 顺序或关键异常 |
services/<service-code>.md |
Service 职责、API/事件、数据、依赖、配置或运行要求 |
glossary.md |
新增、重定义、重命名、歧义、中英不一致或所有权变化 |
没有真实内容就不创建文件。产品架构与技术架构分开；跨视角流程只在 flows/ 维护完整版本，由架构文档引用。Change lifecycle 中，无关历史知识债务进入 follow-up 信号，不扩大当前 Change；会直接导致本 Change 错误的冲突必须处理。maintain 只处理 consumer 明确授权的 targets，不扩大全量知识审计。
3. Assess
检查 proposal、design、delta specs、tasks 和现有 knowledge，创建或更新 Brief，并把真实 impacts 转成 tasks。可在 Change 内维护：
schemaVersion: buildr.knowledge-impact/v1
change: <change-id>
operation: assess
treeIdentity: <identity or planning>
impacts:
- type: brief|overview|product-architecture|technical-architecture|flow|service|glossary
target: <relative path>
reason: <confirmed reason>
status: pending|aligned|updated|unresolved|not-applicable
sourceIdentities: []
unresolvedItems: []
Sidecar 只是 workflow evidence，不是事实源。不把 not-applicable 目标转换为空文档任务。
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.
- 4d ago First seen · 104 lines · 71 tokens per session scan A 9941bf1fdc47
current-knowledge-maintenance is a skill published in the GitHub repository BuildrAI/Buildr (24 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,718 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-08-30.
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…