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 jxoesneon/Ciel --skill cpp-developmentgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/cpp-development)<a href="https://agentmods.dev/skills/jxoesneon/ciel/cpp-development"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/cpp-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jxoesneon/ciel/cpp-development"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/cpp-development.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00449 |
| Opus 5.5 | $0.00010 | $0.00180 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
cpp-development 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 25d 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.
What it actually says
CIEL ADAPTATION: C++ Development (Core Guidelines)
This skill formalizes the use of modern C++ (C++17/20+). it prioritizes resource safety (RAII) and the C++ Core Guidelines.
The Integrity Layer (RAII)
- No Raw Ownership: Never transfer ownership via raw pointers (
T*). Usestd::unique_ptrorstd::shared_ptr. - Resource Binding: Bind all resource lifetimes (Files, Locks, Sockets) to object lifetimes via RAII classes.
- Smart Allocation: Avoid
newanddelete. Usestd::make_uniqueandstd::make_shared.
Architectural Standards
- Immutability: Declaring objects
constorconstexprby default. Member functions must beconstunless they mutate state. - Type Safety: Use
enum classover plainenum. Prohibit C-style casts; usestatic_castordynamic_cast. - Interfaces: Pass "in" parameters by value for cheap types and
const&for expensive types.
TDD & Verification
- Framework: GoogleTest (gtest) + GoogleMock (gmock).
- CMake/CTest: Use
gtest_discover_tests()for stable discovery. Run with--output-on-failure. - Sanitizers: ALWAYS run tests with AddressSanitizer (ASan) and UndefinedBehaviorSanitizer (UBSan) in CI.
Anti-Patterns
- Naked New: Calling
newwithout immediately wrapping it in a smart pointer or RAII class. - Global Variables: Using non-const globals (violates I.2).
- Implicit Conversions: Allowing narrowing/lossy arithmetic conversions without explicit casting.
What ships with it
1 file 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.
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.
- 25d ago Changed · -13 lines ba04e02c6a0d
- 1mo ago First seen · 50 lines · 24 tokens per session scan A 5e20a2ad2d97
cpp-development is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 24 tokens to every session and 449 once invoked, about $0.0001 per session on Opus 5.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
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
blink-gc-plugin
Develop, build, test, and roll changes to the Blink GC Clang plugin (//tools/clang/blinkgcplugin). Use when modifying or adding Oilpan/Blink GC Clang plugin checks, running plugin unit tests, checking Chromium/Blink targets for new plugin violations, suppressing violations with GCPLUGINIGNORE, or force-rolling Clang…
mockery-suite-tests
Use when writing Go tests that need test doubles or cover multiple cases - detect the repo's mocking approach (Mockery v3, gomock, hand-written testify mocks, fakes), table-driven cases, testify suites when the repo uses them, and real-Postgres tests for repository adapters.