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 agents/ysyecust/everything-claude-code/cpp-reviewergit clone --depth 1 https://github.com/ysyecust/everything-claude-codeWhat 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.00041 | $0.00762 |
| Opus 5 | $0.00020 | $0.00381 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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.
This is a copy
100% identical to cpp-reviewer — 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 — 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:
- Run
git diff -- '*.cpp' '*.hpp' '*.cc' '*.hh' '*.cxx' '*.h'to see recent C++ file changes - Run
clang-tidyandcppcheckif available - Focus on modified C++ files
- Begin review immediately
Review Priorities
CRITICAL -- Memory Safety
- Raw new/delete: Use
std::unique_ptrorstd::shared_ptr - Buffer overflows: C-style arrays,
strcpy,sprintfwithout 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()orpopen() - Format string attacks: User input in
printfformat string - Integer overflow: Unchecked arithmetic on untrusted input
- Hardcoded secrets: API keys, passwords in source
- Unsafe casts:
reinterpret_castwithout justification
HIGH -- Concurrency
- Data races: Shared mutable state without synchronization
- Deadlocks: Multiple mutexes locked in inconsistent order
- Missing lock guards: Manual
lock()/unlock()instead ofstd::lock_guard - Detached threads:
std::threadwithoutjoin()ordetach()
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,typedefinstead ofusing
MEDIUM -- Performance
- Unnecessary copies: Pass large objects by value instead of
const& - Missing move semantics: Not using
std::movefor sink parameters - String concatenation in loops: Use
std::ostringstreamorreserve() - Missing
reserve(): Known-size vector without pre-allocation
MEDIUM -- Best Practices
constcorrectness: Missingconston methods, parameters, referencesautooveruse/underuse: Balance readability with type deduction- Include hygiene: Missing include guards, unnecessary includes
- Namespace pollution:
using namespace std;in headers
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 First seen · 74 lines · 41 tokens per session scan A 3b83dc208091
cpp-reviewer is an agent published in the GitHub repository ysyecust/everything-claude-code (43 stars, last pushed 15d ago), 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. It is 100% identical to cpp-reviewer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.