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 commands/mturac/everything-openai-codex/cpp-reviewgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/commands/mturac/everything-openai-codex/cpp-review)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/cpp-review"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/cpp-review.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.00029 | $0.00898 |
| Opus 5 | $0.00015 | $0.00449 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
cpp-review 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 yesterday.
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.
This is a copy
100% identical to cpp-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C++ Code Review
This command invokes the cpp-reviewer agent for comprehensive C++-specific code review.
What This Command Does
- Identify C++ Changes: Find modified
.cpp,.hpp,.cc,.hfiles viagit diff - Run Static Analysis: Execute
clang-tidyandcppcheck - Memory Safety Scan: Check for raw new/delete, buffer overflows, use-after-free
- Concurrency Review: Analyze thread safety, mutex usage, data races
- Modern C++ Check: Verify code follows C++17/20 conventions and best practices
- Generate Report: Categorize issues by severity
When to Use
Use /cpp-review when:
- After writing or modifying C++ code
- Before committing C++ changes
- Reviewing pull requests with C++ code
- Onboarding to a new C++ codebase
- Checking for memory safety issues
Review Categories
CRITICAL (Must Fix)
- Raw
new/deletewithout RAII - Buffer overflows and use-after-free
- Data races without synchronization
- Command injection via
system() - Uninitialized variable reads
- Null pointer dereferences
HIGH (Should Fix)
- Rule of Five violations
- Missing
std::lock_guard/std::scoped_lock - Detached threads without proper lifetime management
- C-style casts instead of
static_cast/dynamic_cast - Missing
constcorrectness
MEDIUM (Consider)
- Unnecessary copies (pass by value instead of
const&) - Missing
reserve()on known-size containers using namespace std;in headers- Missing
[[nodiscard]]on important return values - Overly complex template metaprogramming
Automated Checks Run
# Static analysis
clang-tidy --checks='*,-llvmlibc-*' src/*.cpp -- -std=c++17
# Additional analysis
cppcheck --enable=all --suppress=missingIncludeSystem src/
# Build with warnings
cmake --build build -- -Wall -Wextra -Wpedantic
Example Usage
User: /cpp-review
Agent:
# C++ Code Review Report
## Files Reviewed
- src/handler/user.cpp (modified)
- src/service/auth.cpp (modified)
## Static Analysis Results
✓ clang-tidy: 2 warnings
✓ cppcheck: No issues
## Issues Found
[CRITICAL] Memory Leak
File: src/service/auth.cpp:45
Issue: Raw `new` without matching `delete`
```cpp
auto* session = new Session(userId); // Memory leak!
cache[userId] = session;
Fix: Use std::unique_ptr
auto session = std::make_unique<Session>(userId);
cache[userId] = std::move(session);
[HIGH] Missing const Reference File: src/handler/user.cpp:28 Issue: Large object passed by value
void processUser(User user) { // Unnecessary copy
Fix: Pass by const reference
void processUser(const User& user) {
Summary
- CRITICAL: 1
- HIGH: 1
- MEDIUM: 0
Recommendation: FAIL: Block merge until CRITICAL issue is fixed
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.
- yesterday First seen · 133 lines · 29 tokens per session scan A 58a0e058207b
cpp-review is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 11d ago), licensed MIT. It adds 29 tokens to every session and 898 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cpp-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
evolution-engine
Scan feedback and generate evolution proposals for rule/skill upgrades.
boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
pac-validate
Validate Product as Code project structure and files for specification compliance.
svelte:storybook-troubleshoot
Diagnose and fix common Storybook issues in SvelteKit projects, including build errors, module problems, and configuration issues.
README
Welcome to the Claude Command Suite! This collection of commands is organized into logical namespaces to help you quickly find the right tool for your task.
svelte:migrate
Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes.