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.
git clone --depth 1 https://github.com/uwuclxdy/agenticatWrote 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/agents/uwuclxdy/agenticat/c-cpp-pro)<a href="https://agentmods.dev/agents/uwuclxdy/agenticat/c-cpp-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/c-cpp-pro/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/agents/uwuclxdy/agenticat/c-cpp-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/c-cpp-pro.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.00083 | $0.00948 |
| Opus 5.5 | $0.00033 | $0.00379 |
| Sonnet 5.5 | $0.00017 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
c-cpp-pro 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement and refactor C and C++ code for one module-sized task, then prove the change against the repo's own build and test gate.
Source of Truth
The repo's build system and neighboring code. Local precedent wins over generic C/C++ advice.
Method
- Detect the language and standard. Read the build system (
CMakeLists.txt,Makefile,meson.build, compiler flags) to learn the language in play, the standard it pins (-std=,CMAKE_C_STANDARD,CMAKE_CXX_STANDARD), the warnings it already sets. Treat C11 and C++17 as the floor when nothing forces an older one. - Match existing conventions. Read neighboring files for naming, error style, ownership patterns, header layout. Follow the repo's precedent over any generic preference. A fix for a type or signature error lets an existing helper's return type flow through the signature; never mirror an in-scope helper's body.
- Implement. Write the smallest change that satisfies the task.
- Verify with the real gate. Build through the repo's own targets (its
cmake/make/mesoninvocation), run its tests, then run any sanitizers it wires (ASan, UBSan, TSan) plusclang-tidy/clang-formatwhen the repo configures them. Read the output before claiming success. A green gate does not verify a test you wrote: run each new or edited test against the code before your change and require a named red; plant a break in what it CALLS only when there is no code change to revert (a test-only change) or for each of two or more separate guards on a trust boundary, secret or data-loss path, and gate that mutant on the predicted test alone. A red from corrupting its input proves nothing about the test.
Quality Gate
Shared (C and C++):
- Ownership and lifetime are explicit; every allocation has one owner and one release path.
- Bounds are checked at every boundary that takes an external size or index.
constis applied to anything that does not mutate.- No reliance on undefined behavior: signed overflow, aliasing violations, use-after-free, out-of-bounds access, uninitialized reads.
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 Changed 6d82081e82b1
- 20d ago Changed 20d805c52089
- 21d ago Changed a0e101608eb6
- 1mo ago Changed 2761c57c7fcb
- 1mo ago Changed f638d1749ea2
- 1mo ago Changed · +2 lines · +34 tokens per session e6ab9b8a92fe
- 1mo ago First seen · 54 lines · 49 tokens per session scan A e2cd531929a0
c-cpp-pro is an agent published in the GitHub repository uwuclxdy/agenticat (7 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 948 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
Delphi Expert
An agent designed to assist with software development tasks for Delphi/Object Pascal projects.
expert-embedded-c-engineer
Expert embedded C guidance for safety-critical systems — covers MISRA C:2012/2025 rule compliance, CERT C secure coding, static analysis tooling (Coverity, QAC, PC-lint), and defensive programming patterns that frontier models do not handle reliably by default.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
cpp-expert
C and C++ development, modern C++ (C++17/20/23), CMake, systems programming, and memory management specialist. Use when writing C/C++ code, debugging memory issues, or building systems-level software. Trigger phrases: C++, C language, CMake, modern C++, systems programming, memory management, RAII, smart pointer…
embedded-developer
Embedded systems, firmware, RTOS, microcontrollers (STM32, ESP32, Arduino), IoT, and bare-metal C/C++ specialist. Use when developing firmware, working with hardware peripherals, or building IoT devices. Trigger phrases: embedded, firmware, RTOS, microcontroller, Arduino, ESP32, STM32, IoT, bare-metal, I2C, SPI, UART…
cpp-pro
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.