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/Jorgejie/ai_scaffoldWrote 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/jorgejie/ai_scaffold/cpp-memory-review)<a href="https://agentmods.dev/agents/jorgejie/ai_scaffold/cpp-memory-review"><img src="https://agentmods.dev/badge/agents/jorgejie/ai_scaffold/cpp-memory-review/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/jorgejie/ai_scaffold/cpp-memory-review"><img src="https://agentmods.dev/badge/agents/jorgejie/ai_scaffold/cpp-memory-review.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.00008 | $0.00639 |
| Opus 5.5 | $0.00003 | $0.00256 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (56 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 639 once invoked, about $0.0000 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.
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…
gil-discipline-checker
Use this agent to audit GIL (Global Interpreter Lock) management in C extension code, including foreign C library interaction and free-threaded Python readiness.\n\n \nUser: Check GIL handling in my C extension that wraps a foreign library.\nAgent: I will run the GIL usage scanner, verify matched…