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/nevaberry/nevaberry-plugins/c-cpp-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill c-cpp-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00012 | $0.02379 |
| Opus 5 | $0.00006 | $0.01189 |
| Sonnet 5 | $0.00002 | $0.00476 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade A, and why
c-cpp-knowledge-patch 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C and C++ compatibility guidance
Use this skill when upgrading Clang, GCC, libclang, libstdc++, or C/C++ language modes; diagnosing a compiler-version regression; changing modules, sanitizers, static analysis, formatting, offloading, or target options; or reviewing an ABI boundary built with different toolchain versions.
Treat the project as the source of truth. Inspect its compiler constraints, dialect flags, target triples, standard-library selection, warning policy, sanitizer configuration, module pipeline, and ABI consumers before applying a compatibility switch. Prefer a source migration or a consistent rebuild over leaving a legacy switch in place indefinitely.
Topic index
| Reference | Read when working on |
|---|---|
| C language and standards | C23/C2y modes, C compatibility, declarations, initialization, and conformance gaps |
| C++ language and modules | C++20/23/26/29 features, constexpr, templates, modules, coroutines, and dialect defaults |
| Diagnostics and tooling | warnings, machine-readable diagnostics, clang-format, libclang, AST matchers, plugins, and the Static Analyzer |
| Libraries, builtins, and attributes | libstdc++, builtins, annotations, format checking, and allocation contracts |
| Migration and ABI | mixed compiler objects, mangling, record layout, removed compatibility paths, and library ABI transitions |
| Optimization, debugging, and sanitizers | aliasing, overflow, floating point, LTO, debug information, profiles, and sanitizer controls |
| Targets, offloading, and OpenMP | CPU/OS targets, CUDA/HIP, OpenACC, WebAssembly, OpenMP, and architecture flags |
Upgrade triage: breaking changes first
Pin the intended language dialect
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- coverage.json 1.2 KB
- references/c-language-and-standards.md 7.6 KB
- references/cpp-language-and-modules.md 9.7 KB
- references/diagnostics-and-tooling.md 9.7 KB
- references/libraries-builtins-and-attributes.md 8.5 KB
- references/migration-and-abi.md 6.0 KB
- references/optimization-debugging-and-sanitizers.md 7.1 KB
- references/targets-offloading-and-openmp.md 7.2 KB
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 · 218 lines · 12 tokens per session scan A 3c58039ee72a
c-cpp-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 2,379 once invoked, about $0.0001 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…