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 BuildrAI/Buildr --skill declaration-intakegit 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/declaration-intake)<a href="https://agentmods.dev/skills/buildrai/buildr/declaration-intake"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/declaration-intake/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/buildrai/buildr/declaration-intake"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/declaration-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00042 | $0.01119 |
| Opus 5.5 | $0.00017 | $0.00448 |
| Sonnet 5.5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
declaration-intake 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Declaration Intake Skill
本 Skill 是 Project Declaration Intake 的 Agent 编排入口。它只管理两类 Project-owned 长期声明：
projects/<project>/preparation.yml：Agent按需调用哪些Project/Service真实准备入口；projects/<project>/verification.yml：项目有哪些稳定测试体系、在哪里发现并执行。
Intake 不保存状态、不拥有 schema 或 writer，也不管理 capabilities.yml、commands.yml。缺少 Skill/provider 时交给 Capability 体系；缺少 CLI/runtime 时只报告 Commands/Doctor 诊断。
1. 确认触发与范围
识别trigger：Project注册、Service注册、首次Task scope、依赖/构建/测试入口变化、Preparation declaration/Recipe gap、Verification coverage gap，或用户显式初始化/刷新。
只使用已登记 Project 和本次明确 Project/Service scope。Project-only 不虚构 Service；多 Service 分别列出事实与候选，不复制其他 Service 的结论。不得递归扫描整个仓库、按目录名猜技术栈，或读取 Task lifecycle/current projection 作为声明来源。
2. 只读 Discovery
读取以下最小事实：
- Project/Service registry、各 scope 的真实根与适用规则；
- 当前
preparation.yml、verification.yml和所属 schema； - 明确的 package/build/test wrapper、lockfile或配置、CI与项目文档；
- 当前 Commands/Capability readiness，仅用于外部依赖诊断。
对每个 scope 输出：trigger、当前声明状态、Preparation Recipe 候选/差异、测试地图候选/差异、证据、外部缺口和建议写入。测试地图候选区分证明覆盖范围与路径根，核对完整入口实际覆盖的测试；字段以 task-verification 的当前声明参考为准。旧声明只提供调查线索，结合真实入口重建当前地图，不机械替换版本号。没有稳定事实时标记 gap，不创建技术栈 adapter、测试、wrapper 或工具安装方案。
Discovery、Project/Service注册、Buildr Web GET、Doctor与Task Finish均不得创建、修改或删除长期声明。
3. 区分 routine maintenance 与用户决定
任何写入前都先展示精确diff，并按以下closed条件分类：
routine-maintenance：只让声明追上当前用户目标和已登记scope内已经确认的wrapper、lockfile、build/test入口或既有authority；不新增/删除Project或Service scope，不改变证明范围、路径根、完整入口覆盖或环境边界，不引入新的测试体系、外部效果或安全例外，且authority无冲突。Agent可以在当前用户目标授权内直接交给owner维护并验证，无需让用户承担内部声明步骤。user-decision-required：新增/删除scope，改变证明范围、路径根、完整入口覆盖或环境边界，引入新的测试体系、外部效果或安全例外，或authority证据冲突，且当前授权尚未覆盖该变化。必须在写入前请求用户确认精确变化。
分类与展示至少包含：
- 精确目标文件；
- 新增、修改或删除的 Recipe／测试族身份与 scope；
- 关键 invocation、inputs/outputs、environment/effects 差异；
- 尚未解决的 Commands/Capability 或测试建设缺口。
user-decision-required没有确认时只报告当前缺口与候选；触发检查或Formal Task本身不授予额外写入权。当前有效授权已覆盖对象、长期变化与副作用时直接继续，不按轮次重复确认。routine-maintenance也不得静默扩大scope、伪造测试能力或绕过owner。
4. 交给声明 owner
分类完成后：
- Preparation在
routine-maintenance成立或用户确认长期变化后，由Agent直接维护Project-ownedpreparation.yml并核对真实wrapper、cwd和scope；不创建Application状态； - Verification 在
routine-maintenance成立或用户确认长期变化后，交给task-verificationSkill，使用其 schema、模板和 Doctor 校验。
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 Changed 3ace4c156f62
- 1mo ago Changed · -37 tokens per session de8546067670
- 1mo ago Changed f67ee2b8a058
- 1mo ago First seen · 72 lines · 79 tokens per session scan A ddf90cc6dfb0
declaration-intake is a skill published in the GitHub repository BuildrAI/Buildr (28 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,119 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.