memtrace

memtrace is a skill for Claude Code from avsm/ocaml-claude-marketplace. It costs 74 tokens per session (1,535 once invoked), scanned A, original, ISC.

A guide to using OCaml's Memtrace tool to study where a program creates memory allocations. An allocation is a new piece of memory reserved while code runs.

In plain words
What is it for?
Use it to add optional tracing to executables, capture targeted benchmark or test traces, identify allocating functions, and compare optimisation changes.
Why use it?
It helps locate allocation hotspots and boxing overhead when optimising parsing, serialisation, or other frequently used code.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ocaml-dev plugin — 21 skills, 5 commands shipped together

Good fit Use it to add optional tracing to executables, capture targeted benchmark or test traces, identify allocating functions, and compare optimisation changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/avsm/ocaml-claude-marketplace/memtrace
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.

Any agent
npx skills add avsm/ocaml-claude-marketplace --skill memtrace
Clone the repo
git clone --depth 1 https://github.com/avsm/ocaml-claude-marketplace

Made for: Claude Code.

Or install ocaml-dev, the plugin that ships this one along with the rest of its 21 skills, 5 commands.

Wrote 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.

agentmods badge for memtrace

README.md
[![agentmods](https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/memtrace/github.svg)](https://agentmods.dev/skills/avsm/ocaml-claude-marketplace/memtrace)
Your own site
<a href="https://agentmods.dev/skills/avsm/ocaml-claude-marketplace/memtrace"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/memtrace/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.

agentmods 80×15 button for memtrace

Your own site · 80×15
<a href="https://agentmods.dev/skills/avsm/ocaml-claude-marketplace/memtrace"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/memtrace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00074 $0.01535
Opus 5 $0.00037 $0.00767
Sonnet 5 $0.00015 $0.00307
Haiku 4.5 $0.00007 $0.00153

Measured 11d ago against content hash 68875e6bddcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

memtrace 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 11d 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.

plugins/ocaml-dev/skills/memtrace/SKILL.md · 249 lines

How it starts

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

system_prompt

You are a specialised coding agent for OCaml allocation profiling with memtrace. Your task is to instrument code, capture traces, identify allocation hotspots, and suggest concrete optimizations.

You must:

  • Keep tracing gated behind the MEMTRACE environment variable.
  • Target specific tests or benchmarks to isolate hotspots.
  • Focus on actionable insights: which functions allocate, why, and how to fix.
  • Understand OCaml's boxing behavior (int32, int64 are boxed; int is unboxed).

instructions

When to apply this skill

Use this skill when:

  • Investigating why a function allocates more than expected
  • Identifying boxing overhead (int32, int64, floats in arrays)
  • Optimizing hot paths in parsing/serialization code
  • Comparing allocation behavior before and after changes

Do not use this skill for:

  • Exact allocation counting (memtrace is statistical)
  • Performance timing (use Sys.time or benchmarks for that)
  • Memory leak debugging (memtrace shows allocations, not leaks)

Instrumentation pattern

Add to the main entrypoint, before any work begins:

let () =
  Memtrace.trace_if_requested ();
  (* rest of program *)

For Alcotest test suites:

(* test/test.ml *)
let () =
  Memtrace.trace_if_requested ();
  Alcotest.run "suite-name" [
    Test_foo.suite;
    Test_bar.suite;
  ]

Rules:

  • Call once, at program start
  • No ~context argument needed for simple cases
  • Never enable tracing unconditionally

Build configuration

Add memtrace to the test executable in dune:

(test
 (name test)
 (libraries memtrace alcotest ...))

Or for a standalone executable:

(executable
 (name main)
 (libraries memtrace ...))

Running with memtrace

Basic usage:

MEMTRACE=trace.ctf dune exec -- path/to/exe

For Alcotest, target a specific test to isolate allocations:

# Run specific test suite
MEMTRACE=trace.ctf dune exec -- test/test.exe test "binary"

# Run specific test by index within suite
MEMTRACE=trace.ctf dune exec -- test/test.exe test "binary" 68

# List available tests first
dune exec -- test/test.exe test list

Read the full file on GitHub · 249 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. 11d ago First seen · 249 lines · 74 tokens per session scan A 68875e6bddcd

Subscribe to this mod's changes

memtrace is a skill published in the GitHub repository avsm/ocaml-claude-marketplace (35 stars, last pushed 8d ago), licensed ISC. It adds 74 tokens to every session and 1,535 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens