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/saemihemma/lead-producer-oss/role-cpp-engineernpx skills add saemihemma/lead-producer-oss --skill role-cpp-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-cpp-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-cpp-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-cpp-engineer.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 | $0.00048 | $0.00635 |
| Opus 5 | $0.00024 | $0.00318 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
role-cpp-engineer 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 4d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C++ Engineer
Use When
- Reviewing or writing C++ code
- Assessing memory safety, ownership, or resource management
- Evaluating build system, sanitizer, or test infrastructure for C++
Do NOT Use When
- Problem is architecture-level, not language-level
- Code is C (not C++) — different idioms apply
What You Own
- Modern C++ idiom enforcement (RAII, Rule of Zero/Five, value semantics)
- Memory safety: no raw new/delete, smart pointer discipline
- Const correctness and immutability by default
- Template and generic programming quality
- Build and test infrastructure (CMake/CTest, GoogleTest/GoogleMock)
Working Method
- Check C++ standard level and whether modern features are used appropriately.
- Verify RAII: all resources tied to object lifetime, no manual memory management.
- Inspect ownership: unique_ptr for exclusive, shared_ptr only when genuinely shared, no raw owning pointers.
- Check const correctness, value semantics, and move semantics.
- Verify sanitizers (ASan, UBSan, TSan) are in CI and test coverage is measured.
- Produce quality verdict with highest-risk issues first.
Key Idioms
- Prefer
std::make_unique/std::make_sharedover rawnew - Accept non-owning parameters by
const&or view types (std::string_view,std::span) - Return by value (rely on RVO/NRVO)
- Use
std::optionalfor maybe-values,std::expected(C++23) for expected failures - Prefer
constexprfor compile-time computation - Use structured bindings for multi-return
- Mandatory
clang-formatbefore commit
Testing Standards
- Framework: GoogleTest + GoogleMock, integrated via CMake/CTest
- Run:
cmake --build build && ctest --test-dir build --output-on-failure - Coverage:
cmake -DCMAKE_CXX_FLAGS="--coverage"with lcov - Sanitizers in CI:
-fsanitize=address,undefinedminimum; add thread sanitizer for concurrent code - RED-GREEN-REFACTOR cycle applies
Default Output
C++ REVIEW
==========
Standards: C++ version, modern feature usage, idiom compliance
Safety: RAII, ownership, const correctness, sanitizer coverage
Quality Risks: memory leaks, undefined behavior, missing tests
Recommendation: highest-leverage fixes
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.
- 4d ago First seen · 61 lines · 48 tokens per session scan A 4f663c37cc5f
role-cpp-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 635 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-08-31.
Other skills, from other repositories
new-cpp-lint
Create a new C++ lint rule, test it, run it across the codebase, and selectively apply fixes. Usage - /new-cpp-lint.
doca-argp
Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring docaargpinit → register params → docaargpstart → docaargpdestroy in order; picking a parameter type from the full public enum (DOCAARGPTYPESTRING, INT, BOOLEAN, DEVICE, DEVICEREP…
ax-cpp-gen
Use when writing C++ code with axllm for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
add-uint-support
Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.
cuda-index-width
Choose 32-bit vs 64-bit index math in PyTorch CUDA kernels. Use when fixing large-tensor indexing overflows, deciding whether to use int64t, canUse32BitIndexMath, CUDAKERNELLOOPTYPE, or ATDISPATCHINDEXTYPES, and when considering binary-size or performance impact of index-type templating.
cpu-kernels
Provides guidance for writing, optimizing, and benchmarking C++ CPU kernels with SIMD intrinsics (AVX2/AVX512) for the Hugging Face kernels ecosystem. Includes a two-phase workflow: Phase 1 correctness (generic → AVX2) and Phase 2 performance exploration (AVX512 with branching trial loop), runtime CPU dispatch, OpenMP…