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 openspec-contract-guardgit 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/openspec-contract-guard)<a href="https://agentmods.dev/skills/buildrai/buildr/openspec-contract-guard"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/openspec-contract-guard.svg" alt="Measured on agentmods" 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.00071 | $0.01563 |
| Opus 5 | $0.00036 | $0.00781 |
| Sonnet 5 | $0.00014 | $0.00313 |
| Haiku 4.5 | $0.00007 | $0.00156 |
Grade A, and why
openspec-contract-guard 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 today.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Contract Guard
父子任务场景保持单一规范责任：同一个具体规范变化在同一时间只能由一个活跃变更负责。计划文档不复制子任务规范；父任务亲自实现集成能力时才创建自身的窄变更。范围调整后核对实际重叠，不靠重复归档覆盖冲突。
本 Skill 只保留 OpenSpec 1.6 未提供的 Buildr 契约保证：apply前的语义就绪预检、并行 active change 冲突、确定性 expected tree、隔离严格验证、条件式 canonical 写入、写后确认和基于文件事实的断点恢复。
OpenSpec 1.6 负责 delta 格式与 Requirement 结构、单个 change 的规范校验、canonical spec 重建和 archive 的场景保全检查。先运行上游 openspec validate <change> --strict；本 Skill 不重复实现这些解析或 archive 安全规则。
本 Skill 不修改外部 openspec-* Skills、外部 OpenSpec CLI 或本机 CLI 安装。
1. Apply 前门禁
change artifacts complete 且上游严格验证通过后运行：
openspec validate <change> --strict
buildr openspec convergence preflight <change> --project <project> --target <actual-work-root> --json
<actual-work-root>必须是Agent已核对的当前Workspace或matching Worktree根。Preflight只读复用正式convergence planner、active Change scan和projected strict validation，不检查实现期checklist，不写canonical、Receipt、archive、Task或Review事实。它把blocked区分为active-change-conflict、scenario-omission、identity-conflict、projected-validation与其他semantic-resolution-required：Agent只处理对应依赖、Change artifact语义或用户决定，再重新运行strict与preflight，不得自动补回Scenario、选择rename或修改canonical。
只有preflight返回current ready后才继续apply。Agent直接读取当前OpenSpec artifacts，必要时使用OpenSpec返回的identity作为Planning Review subject；不调用额外规划身份接口，也不保存研发快照。Preflight blocked时停止apply，禁止把blocker写入Review Result代替处理。Review不是apply门禁，也不拥有、不复制或解释preflight逻辑。Buildr不提供baseline/create或阶段型check，也不创建、刷新、读取或依赖这些sidecar。
ready只绑定本次delta、canonical、全部active Change observation与OpenSpec executable/algorithm identity；任一事实变化后旧ready陈旧。它不是写入授权，也不替代实现验证。最终buildr openspec converge永远重新读取最新事实、重新规划并重新验证，不接受或读取旧preflight结果。
2. 单一收敛事务
openspec validate <change> --strict
buildr openspec converge <change> --project <project> --target <actual-work-root> --json
<actual-work-root>必须是Agent已按Git checkout、Project/Service registry与可选Worktree evidence核对的真实Change根，不得从cwd、分支名、路径相似或旧Receipt猜测。target中看不到active Change时保持零写入，按CLI next action纠正实际root。
产品计算单一 identity/plan，在临时 Project 投射 expected files并运行 validate --all --strict；随后重验 delta、executable 与全部 canonical before digests，条件一致才替换文件。首次canonical mutation前写入唯一事务期.buildr/convergence-receipt.json；写后只确认expected digests与真实strict validation，再执行archive --skip-specs，正常archive成功后释放本次Receipt再返回passed。
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.
- today Changed fea471330142
- 4d ago Changed 34c3561be6ab
- 8d ago First seen · 66 lines · 71 tokens per session scan A e3ea1b3ca847
openspec-contract-guard 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,563 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…