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/leandrosilvaferreira/claude-plugins-registry/cpp-testingnpx skills add leandrosilvaferreira/claude-plugins-registry --skill cpp-testinggit clone --depth 1 https://github.com/leandrosilvaferreira/claude-plugins-registryWrote 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/leandrosilvaferreira/claude-plugins-registry/cpp-testing)<a href="https://agentmods.dev/skills/leandrosilvaferreira/claude-plugins-registry/cpp-testing"><img src="https://agentmods.dev/badge/skills/leandrosilvaferreira/claude-plugins-registry/cpp-testing.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.1 | $0.00034 | $0.02349 |
| Opus 5 | $0.00017 | $0.01175 |
| Sonnet 5 | $0.00007 | $0.00470 |
| Haiku 4.5 | $0.00003 | $0.00235 |
Grade A, and why
cpp-testing 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 327 lines · 34 tokens per session scan A c0047d528cea
cpp-testing is a skill published in the GitHub repository leandrosilvaferreira/claude-plugins-registry (5 stars, last pushed 2d ago), with no licence file. It adds 34 tokens to every session and 2,349 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
create-cpp-tests
Create a new cpptests entry for validating a C++ interface vtable layout against binary reference YAMLs. Creates the .cpp test file in cpptests/ and appends a configs/ .yaml entry under cpptests:. Use when a user asks to add vtable layout validation for a new hl2sdkcs2 interface class.
run-c-unit-tests
Run C/C++ unit tests to verify correctness. Use this after making changes to C code to verify nothing is broken.
cpp-project-setup
Modern C++ project setup: CMake/CMakePresets, vcpkg, Ninja, VS Code/clangd, GoogleTest, clang-format/tidy, Doxygen, CI, macOS/Linux/Windows. Use for bootstrapping or modernizing host-side C++ apps and libraries; prefer embedded-project-setup for MCU firmware and cross-debug flows.
cpp-development
Modern C++ (17/20+) standards based on Core Guidelines, RAII, and GoogleTest.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
cpp-testing
C++ testing workflow for unit and integration tests: GoogleTest/GoogleMock, CMake/CTest integration, diagnosing flaky tests, and running sanitizers and coverage for correctness signal. Use when writing or fixing C++ tests and test infrastructure.