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/mcpp-community/mcpp/mcpp-releasenpx skills add mcpp-community/mcpp --skill mcpp-releasegit clone --depth 1 https://github.com/mcpp-community/mcppWhat 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.00046 | $0.04895 |
| Opus 5 | $0.00023 | $0.02448 |
| Sonnet 5 | $0.00009 | $0.00979 |
| Haiku 4.5 | $0.00005 | $0.00490 |
Grade A, and why
mcpp-release scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| mirror leg 报 `missing/unverified` | 资产没传上去或还没传播 | 先 GET 核验(**必须 GET,`curl -I` 会骗你**),gitcode 用 `gitcode.com` 直链而非 `api.` 主机;确认缺件后本地补传再 `gh run rerun --failed`(脚本幂等,已验证的资产会跳过) | How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcpp 版本发布流程
版本号规范
格式:YYYY.M.D.N(日期版本,月/日不补零),例如 2026.7.27.1。
自 2026.7.27.1 起启用,此前为 0.0.x。与 xlings 生态一致(xlings 于同日从 0.4.70 迁入)。
第 4 段的语义:
.0保留给正式版本 / 稳定版本。日常迭代默认从.1开始。
即一天内可发 .1、.2、.3 …… 若干次常规版本;.0 只在该版本被认定为正式 release 或稳定版时使用。
跨方案的序是单调的:0.0.109 < 2026.7.27.1,第一段从 0 变 2026,不存在回退。
比较逻辑见
src/version_req.cppm。它支持 4 段;改动那里时务必保证str()精确回写,src/pm/resolver.cppm用它重建依赖版本串,会流向 lock 文件与 xlings wire 地址。 尤其.0结尾的版本不能塌成三段。
Overview
mcpp 有 三个持久化版本位置,以及 ci-fresh-install 的一个运行时推导值。它们分属
两组,在不同时间更新;把"正在构建的版本"与 bootstrap pin 一起前移会让 CI 尝试安装
尚未发布的 mcpp。
第一组:正在构建的版本(发布时改,走 bump PR)
mcpp.toml→[package].version— 构建系统读取的项目版本,release.yml 由它推导 tagsrc/version.cppm→MCPP_VERSION— 编译期硬编码常量(--version输出、BMI 指纹、E0006 索引底线比较)
这两处必须在同一个 commit 里一起改:tests/e2e/01_help_and_version.sh 交叉比对
mcpp.toml 与 mcpp --version,只改一处 CI 立刻红。
第二组:bootstrap pin —— CI 用哪个 mcpp 来自举(发布并进索引之后才可改)
.xlings.json→workspace.mcpp— CI bootstrap 装哪个 mcpp
.xlings.json 必须指向一个已经发布、镜像并进入索引的版本。因此它在 bump PR 中
保持已有的可安装版本,直到发布收尾时才可前移。
ci-fresh-install.yml 的 MCPP_PIN 不是持久化 pin:wait-index 从最新 GitHub
Release 推导一次,所有安装 job 消费同一个输出。绝不能手工编辑或恢复字面量
MCPP_PIN,否则 index guard 和实际安装版本会再次漂移。
.github/tools/check_version_pins.sh 校验版本关系和 xlings pin:
bash .github/tools/check_version_pins.sh
必须用 bash 跑,不能用 sh。 脚本用了进程替换(done < <(...)),POSIX
sh/dash 解析不了,用 sh 调用会在第 95 行附近报 Syntax error: redirection unexpected。那是调用它的 shell 的问题,不是脚本的缺陷 —— 它的 shebang 是
#!/usr/bin/env bash,CI 也是用 bash 调的。别据此把这条 guard 当成坏的而跳过:
它是唯一能机器化捕捉 pin 漂移的东西。
也不要通过修改文档或 workflow 绕开动态 MCPP_PIN 设计。src/platform/xlings/xlings.cppm 的
pinned::kXlingsVersion 仍是 xlings 版本的唯一真源。
发布步骤
1. 确认 main 分支状态
git checkout main && git pull origin main
# 确认 CI 全部通过
gh run list --branch main --limit 3
以分支保护和 gh pr checks <pr-number> 显示的 actual required checks 为准。
在 main 上监控当前运行时,检查 ci-linux、ci-linux-e2e、ci-macos、
ci-macos-e2e、ci-windows、ci-windows-e2e 与 cross-build-test 的结果;
跳过或非 required 的 workflow 不是合入 gate。不要在 required CI 红的时候发版。
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.
- yesterday First seen · 328 lines · 46 tokens per session scan A a5e80182abfe
mcpp-release is a skill published in the GitHub repository mcpp-community/mcpp (114 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 4,895 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
readable-cpp
Readable C/C++/Rust/CUDA code rules inspired by The Art of Readable Code. Use when writing, reviewing, or refactoring C, C++, Rust, or CUDA code. Enforces short functions, flat control flow, clear naming, readable structure, and idiomatic patterns.
cpp
Comprehensive C/C++ programming reference covering everything from C11-C23 and C++11-C++23, system programming, CUDA GPU computing, debugging tools, Rust interop, and advanced topics. Use for: C/C++ questions, C/C++ interview preparation, modern language features, RAII/memory management, templates/generics, CUDA…
mcpp-style-ref
为 mcpp 项目应用 Modern/Module C++ (C++23) 编码风格。适用于编写或审查带模块的 C++ 代码、命名标识符、组织 .cppm/.cpp 文件,或用户提及 mcpp、module C++、现代 C++ 风格时。.
mbun-runtime-debugging
调试 mbun 运行时测试失败/崩溃时用。提供仓库实测可用的定位配方——选二进制、单文件跑测、gdb 抓 backtrace、按 API 定位源码、常见坑排查清单、何时跳过。凡处理 bun 测试跑不过/段错误/hang/断言失败,先读本 skill 再动手,避免每个 task 重复摸索拖慢。.
dev-process
在本仓开发任何改动前用。规定 issue 先行的开发流程,按 bugfix / 优化 / 新功能分流;新功能须经 issue 充分讨论并在 .agents/docs 落地设计方案;衔接 tdd-workflow 与本体验证 / 测试 / CI / PR 规范。开发前先读本 skill。.
issue-reporting
向本仓提交 issue / 发起讨论时用。规定一份好问题反馈的 SOP——软件/版本、报错信息、初步分析、相关资料,并去除本地隐私(用户名/token 等替换)。凡要创建 issue、反馈 bug、发起讨论,先读本 skill 再动手。.