check-memory

A code-review check for memory handling in one C or Zig module. It looks for mistakes involving allocated memory, borrowed data, garbage collection, and cleanup.

In plain words
What is it for?
Use it to review C or Zig code for leaks, invalid lifetimes, incorrect ownership, missing guards around garbage collection, and unsafe realloc usage.
Why use it?
It helps catch memory that is used after it is gone, never released, or hidden from the garbage collector. It also checks error paths and unsafe resizing patterns.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/leifericf/agentic-sdk/check-memory
Any agent
npx skills add leifericf/agentic-sdk --skill check-memory
Clone the repo
git clone --depth 1 https://github.com/leifericf/agentic-sdk

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00036 $0.01081
Opus 5 $0.00018 $0.00541
Sonnet 5 $0.00007 $0.00216
Haiku 4.5 $0.00004 $0.00108

Measured 2d ago against content hash 3eecbd2b9a10, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-memory 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.

skills/check-memory/SKILL.md · 110 lines

How it starts

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

check-memory

Role: review the assigned C or Zig module for memory defects.

Failure model: an allocation outlives its owner, a borrow outlives its backing memory, or a GC-visible pointer is held across an allocation point without a guard; the bug that ships is the path that skips a free or the scanner happens to hide.

Active only when the descriptor's :languages includes :c or :zig. Read the ownership rules in skills/shared/references/architecture.md (the C and Zig sections) and any project-specific known-pitfalls note before sweeping.

The bug class splits by language.

Look for

C (GC or manual ownership)

  1. GC windows. Any GC-visible pointer or raw buffer held across an allocation point without a pin or a depth guard. Check pin and unpin pairing on every path, including the error path (the save-stack assertion often fires only in debug builds).
  2. Ownership violations. free on a GC-owned value; a GC value stored in host-owned memory the tracer cannot see; a peek or get result freed or retained past the next collection; a take result leaked.
  3. realloc misuse. p = realloc(p, n) without a temp; the old block leaks when realloc fails.
  4. Error-path leaks. For each early return or longjmp out of a function that allocated host memory: what frees it?
  5. Write-barrier gaps. Direct stores into old-generation objects that bypass the barrier (mutation outside the provided mutators).

Zig (explicit allocators, no GC)

  1. Missing defer or errdefer. Every heap allocation must have a matching free reachable on every path. defer for the success path; errdefer for the partial-construction path before ownership transfers to the caller. Check each early return, each try, each error exit: what frees the buffers allocated above it?
  2. Wrong allocator for the phase. A per-node scratch allocated from the execution allocator (or vice versa); a value meant to outlive parsing allocated from the parse arena; a long-lived entry on a short-lived arena. Match the allocation to its phase.
  3. Slices and pointers outliving backing memory. A slice returned from or stored past the deinit of the allocator that produced it; a sub-slice retained after the parent is freed; a value that aliases a freed source buffer.
  4. init and deinit pairing. Every type with an init or alloc constructor needs a deinit that frees exactly what it owns, called on every path. Double-free (freeing a borrowed slice the owner also frees); missing-free (a field allocated in init not released in deinit).
  5. Allocator passed explicitly. No hidden global allocator; the allocator is a parameter threaded through. Flag any subsystem that reaches for a package-level allocator instead of the one its caller passed.
  6. Alignment and realloc. An @alignCast without a real guarantee; a realloc whose result is dropped on failure (the old block leaks).

Read the full file on GitHub · 110 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. 2d ago First seen · 110 lines · 36 tokens per session scan A 3eecbd2b9a10

Subscribe to this mod's changes

check-memory is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 1,081 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens