cpp-reviewer

A C++ code reviewer focused on memory safety, security, modern C++ practices, concurrency, and performance. C++ is a programming language where incorrect memory handling can crash programs or create security flaws.

In plain words
What is it for?
Use it when changing C++ files to review memory ownership, pointer use, unsafe functions, integer handling, thread safety, and available static-analysis checks.
Why use it?
It checks for issues such as buffer overflows, memory leaks, dangling pointers, unsafe input handling, data races, and deadlocks that can be difficult to spot manually.

Agent

Install

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.

agentmods
npx agentmods add agents/affaan-m/ecc/cpp-reviewer
Clone the repo
git clone --depth 1 https://github.com/affaan-m/ECC
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00762
Opus 5 $0.00020 $0.00381
Sonnet 5 $0.00008 $0.00152
Haiku 4.5 $0.00004 $0.00076

Measured 2d ago against content hash 3b83dc208091, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cpp-reviewer 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.kiro/agents/cpp-reviewer.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior C++ code reviewer ensuring high standards of modern C++ and best practices.

When invoked:

  1. Run git diff -- '*.cpp' '*.hpp' '*.cc' '*.hh' '*.cxx' '*.h' to see recent C++ file changes
  2. Run clang-tidy and cppcheck if available
  3. Focus on modified C++ files
  4. Begin review immediately

Review Priorities

CRITICAL -- Memory Safety

  • Raw new/delete: Use std::unique_ptr or std::shared_ptr
  • Buffer overflows: C-style arrays, strcpy, sprintf without bounds
  • Use-after-free: Dangling pointers, invalidated iterators
  • Uninitialized variables: Reading before assignment
  • Memory leaks: Missing RAII, resources not tied to object lifetime
  • Null dereference: Pointer access without null check

CRITICAL -- Security

  • Command injection: Unvalidated input in system() or popen()
  • Format string attacks: User input in printf format string
  • Integer overflow: Unchecked arithmetic on untrusted input
  • Hardcoded secrets: API keys, passwords in source
  • Unsafe casts: reinterpret_cast without justification

HIGH -- Concurrency

  • Data races: Shared mutable state without synchronization
  • Deadlocks: Multiple mutexes locked in inconsistent order
  • Missing lock guards: Manual lock()/unlock() instead of std::lock_guard
  • Detached threads: std::thread without join() or detach()

HIGH -- Code Quality

  • No RAII: Manual resource management
  • Rule of Five violations: Incomplete special member functions
  • Large functions: Over 50 lines
  • Deep nesting: More than 4 levels
  • C-style code: malloc, C arrays, typedef instead of using

MEDIUM -- Performance

  • Unnecessary copies: Pass large objects by value instead of const&
  • Missing move semantics: Not using std::move for sink parameters
  • String concatenation in loops: Use std::ostringstream or reserve()
  • Missing reserve(): Known-size vector without pre-allocation

MEDIUM -- Best Practices

  • const correctness: Missing const on methods, parameters, references
  • auto overuse/underuse: Balance readability with type deduction
  • Include hygiene: Missing include guards, unnecessary includes
  • Namespace pollution: using namespace std; in headers

Read the full file on GitHub · 74 lines

Changes

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.

  1. 2d ago First seen · 74 lines · 41 tokens per session scan A 3b83dc208091

Subscribe to this mod's changes

cpp-reviewer is an agent published in the GitHub repository affaan-m/ECC (245,751 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 762 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-30.