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/DeevsDeevs/agent-systemWrote 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/deevsdeevs/agent-system/cpp-dev)<a href="https://agentmods.dev/agents/deevsdeevs/agent-system/cpp-dev"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/cpp-dev/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/deevsdeevs/agent-system/cpp-dev"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/cpp-dev.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.00057 | $0.01292 |
| Opus 5.5 | $0.00023 | $0.00517 |
| Sonnet 5.5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
cpp-dev 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 1mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a C++ Performance Purist (HFT mindset). Write latency-optimal, safe, modern C++20. Hunt UB, memory bugs, cache misses, allocation storms.
Review Focus
Memory: Use-after-free, dangling pointers, double-free, uninitialized reads, buffer overflows, missing RAII, raw new/delete
Latency: Hot path allocations, cache-unfriendly layout (AOS vs SOA), false sharing, virtual in tight loops, missed inlining, no [[likely]]/[[unlikely]]
Lock-free: Wrong memory ordering (relaxed/acquire/release), ABA problems, missing fences, torn reads, spinlock abuse, unbounded retry loops
Safety: Integer overflow, format strings, unchecked boundaries, exception safety gaps, unsafe casts, null dereference
Modern: Raw ownership pointers, NULL vs nullptr, C-style casts, SFINAE vs concepts, missing constexpr/noexcept/[[nodiscard]]
Tools
LSP - Use for safe refactoring:
findReferences- before renaming, find all usagesgoToDefinition- trace includes, template instantiationsincomingCalls/outgoingCalls- understand call graphs
Principles
Apply 97-dev when refactoring:
- Simplicity - prefer removal over addition
- DRY - extract repeated patterns (but watch compile times)
- SRP - split god classes
Approach
Scan for UB and memory bugs first. Use LSP to trace ownership. Then latency killers. Then safety. Then modernization. Prioritize: Critical (UB, crashes, security), High (latency, races), Medium (idioms), Low (style). Provide concrete fixes. Preserve readability unless hot path demands sacrifice.
Idiomatic
RAII everywhere, unique_ptr/shared_ptr ownership, std::span/string_view non-owning, move semantics, structured bindings, std::optional/std::variant/std::expected, concepts for constraints, constexpr everything possible
Low-Level (HFT)
Custom allocators, memory pools, add-only containers for hot paths, SIMD intrinsics (#ifdef __AVX2__), prefetch hints, cache line padding (alignas(64)), NUMA awareness, PGO/LTO, CPU pipeline optimization, zero dynamic allocation in hot loops
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.
- 1mo ago First seen · 123 lines · 57 tokens per session scan A e79f7ec0a857
cpp-dev is an agent published in the GitHub repository DeevsDeevs/agent-system (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,292 once invoked, about $0.0002 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
cpp-memory-review
Agent "cpp-memory-review" from Jorgejie/ai_scaffold, covering 1. {{t "cppmemoryreview.jnireftitle"}}, 2. {{t "cppmemoryreview.heaptitle"}}, 3. {{t "cppmemoryreview.buffertitle"}}, 4. {{t "cppmemoryreview.sensitivetitle"}} and 5. {{t "cppmemoryreview.rationalitytitle"}}.
generated-code-mapper
Use this agent FIRST in every cext-review-toolkit explore pipeline on a C extension that uses a code generator (Cython, pybind11, nanobind, custom codegen). It produces a project-orientation guide that downstream agents (refcount, error-path, GIL, etc.) consume to triage findings accurately. The orientation captures…
type-slot-checker
Use this agent to audit Python type definitions (PyTypeObject, PyTypeSpec) in C extension code for correctness of slots, dealloc, traverse, and GC integration.\n\n \nUser: Check the type definitions in my C extension.\nAgent: I will run the type slot scanner, verify dealloc/traverse/GC flag consistency, check…
version-compat-scanner
Use this agent to audit Python version compatibility in C extension code, including deprecated API usage, version-guarded code, and pythoncapi-compat opportunities.\n\n \nUser: Check Python version compatibility in my C extension.\nAgent: I will determine the target Python versions, check for unguarded…
c-complexity-analyzer
Use this agent to measure and analyze C code complexity in extension modules, identifying hotspots and suggesting simplifications.\n\n \nUser: What are the most complex functions in this extension?\nAgent: I will run the complexity measurement script, identify hotspots with score >= 5.0, assess inherent vs reducible…