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/jorgejie/ai_scaffold/cpp-memory-reviewgit clone --depth 1 https://github.com/Jorgejie/ai_scaffoldWhat 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.00008 | $0.00639 |
| Opus 5 | $0.00004 | $0.00319 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
cpp-memory-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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{t "cpp_memory_review.title"}}
{{t "cpp_memory_review.intro"}}
{{t "cpp_memory_review.dimensions_title"}}
1. {{t "cpp_memory_review.jni_ref_title"}}
{{t "cpp_memory_review.jni_ref_desc"}}
{{t "cpp_memory_review.jni_ref_table_header"}} |--------|---------|---------| {{t "cpp_memory_review.jni_ref_row1"}} {{t "cpp_memory_review.jni_ref_row2"}} {{t "cpp_memory_review.jni_ref_row3"}} {{t "cpp_memory_review.jni_ref_row4"}} {{t "cpp_memory_review.jni_ref_row5"}}
{{t "cpp_memory_review.jni_ref_method_title"}} {{t "cpp_memory_review.jni_ref_method_steps"}}
2. {{t "cpp_memory_review.heap_title"}}
{{t "cpp_memory_review.heap_table_header"}} |--------|---------|---------| {{t "cpp_memory_review.heap_row1"}} {{t "cpp_memory_review.heap_row2"}} {{t "cpp_memory_review.heap_row3"}}
{{t "cpp_memory_review.heap_method_title"}} {{t "cpp_memory_review.heap_method_steps"}}
3. {{t "cpp_memory_review.buffer_title"}}
{{t "cpp_memory_review.buffer_table_header"}} |--------|---------|---------| {{t "cpp_memory_review.buffer_row1"}} {{t "cpp_memory_review.buffer_row2"}} {{t "cpp_memory_review.buffer_row3"}} {{t "cpp_memory_review.buffer_row4"}}
4. {{t "cpp_memory_review.sensitive_title"}}
{{t "cpp_memory_review.sensitive_table_header"}} |--------|---------|---------| {{t "cpp_memory_review.sensitive_row1"}} {{t "cpp_memory_review.sensitive_row2"}}
5. {{t "cpp_memory_review.rationality_title"}}
{{t "cpp_memory_review.rationality_table_header"}} |--------|---------|---------| {{t "cpp_memory_review.rationality_row1"}} {{t "cpp_memory_review.rationality_row2"}} {{t "cpp_memory_review.rationality_row3"}} {{t "cpp_memory_review.rationality_row4"}} {{t "cpp_memory_review.rationality_row5"}} {{t "cpp_memory_review.rationality_row6"}}
{{t "cpp_memory_review.output_title"}}
{{t "cpp_memory_review.output_content"}}
{{t "cpp_memory_review.flow_title"}}
{{t "cpp_memory_review.flow_content"}}
{{t "cpp_memory_review.constraints_title"}}
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.
- 3d ago First seen · 85 lines · 8 tokens per session scan A 9223ccad3e4a
cpp-memory-review is an agent published in the GitHub repository Jorgejie/ai_scaffold (52 stars, last pushed 22d ago), licensed MIT. It adds 8 tokens to every session and 639 once invoked, about $0.0000 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.
Other agents, from other repositories
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
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.
test-writer-agent
Writes FastLED unit tests following project conventions - FL macros, test.h patterns, file placement, and simplicity principles.
test-agent
Runs test suite and reports pass/fail status.
CppCoder
Use when: writing or modifying C++ implementation code, refactoring internal logic, implementing features behind the C ABI layer, writing tests, fixing bugs in .cc/.h files, optimizing performance, reviewing code for C++ Core Guidelines compliance, serializing/deserializing JSON, reducing code duplication.
Reviewer
Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.