Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
openai avatar

Ios Memgraph Leaks

  • 56 installs
  • 4.9k repo stars
  • Updated July 14, 2026
  • openai/plugins

ios-memgraph-leaks is an agent skill for capturing iOS simulator memgraphs, summarizing leaks, and proving retain-cycle fixes with scripts.

About

The ios-memgraph-leaks skill helps prove iOS memory leaks from live simulator processes or existing memgraph files using bundled capture and summarize scripts. The workflow builds and drives the reproduction flow, captures a memgraph with capture_sim_memgraph.sh using simulator UDID and bundle identifier, summarizes leaks via summarize_memgraph_leaks.py, and inspects app-owned types with leaks traceTree or groupByType evidence. Fixes require the smallest root-cause patch retaining-edge removal rather than broad cleanup, then recapture on the same simulator with before-and-after leak counts and disappeared types. Agents must not claim fixes from smaller memgraphs alone without explaining ownership paths. SKILL_DIR resolves to the loaded plugin folder, not the target app repo. Pair with ios-debugger-agent when builds, UI driving, logs, or screenshots are also needed. Triggers include debugging leaked objects, retain cycles, or memory growth on iOS simulators.

  • Captures simulator memgraphs with capture_sim_memgraph.sh.
  • Summarizes leaks via summarize_memgraph_leaks.py output.
  • Requires ownership trace or grouped leak tree evidence.
  • Mandates before-and-after recapture to prove fixes.
  • Pairs with ios-debugger-agent for full simulator workflows.

Ios Memgraph Leaks by the numbers

  • 56 all-time installs (skills.sh)
  • +12 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #585 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

ios-memgraph-leaks capabilities & compatibility

Capabilities
simulator memgraph capture scripting · leak summarization with trace limits · ownership path and groupbytype analysis · before after leak regression proof · root cause retaining edge fix guidance
Use cases
debugging · testing
From the docs

What ios-memgraph-leaks says it does

Capture and inspect iOS leaks and memgraphs.
SKILL.md
Do not claim a leak fix from a smaller memgraph alone.
SKILL.md
npx skills add https://github.com/openai/plugins --skill ios-memgraph-leaks

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs56
repo stars4.9k
Last updatedJuly 14, 2026
Repositoryopenai/plugins

How do I prove an iOS leak fix with memgraph evidence from the simulator?

Capture iOS simulator memgraphs, summarize leaked objects, trace ownership paths, and prove before-and-after leak fixes with scripts.

Who is it for?

iOS developers debugging simulator leaks, retain cycles, or memory growth with memgraph tooling.

Skip if: Skip for Android memory profiling, production device-only issues without simulator reproduction, or UI-only debugging.

When should I use this skill?

User debugs iOS leaked objects, retain cycles, memory growth, or needs memgraph before-after evidence.

What you get

Memgraph captures, leak summaries, ownership traces, and before-after proof of disappeared leaked types.

Files

SKILL.mdMarkdownGitHub ↗

iOS Memgraph Leaks

Use this skill to prove iOS leaks from a live simulator process or an existing .memgraph. Pair it with ../ios-debugger-agent/SKILL.md when the task also needs simulator build, install, launch, UI driving, logs, or screenshots.

Core Workflow

1. Build, launch, and drive the exact flow that should release objects. 2. Capture a memgraph from the running simulator process with scripts/capture_sim_memgraph.sh. 3. Summarize leaks with scripts/summarize_memgraph_leaks.py. 4. For each app-owned leaked type, inspect ownership with leaks --traceTree=<address> <file.memgraph> and grouped leak evidence. 5. Make the smallest root-cause patch, then recapture the same flow on the same simulator when possible. 6. Report proof: before/after leak counts, disappeared root types, remaining leaks, memgraph paths, and test/build results.

Do not claim a leak fix from a smaller memgraph alone. A credible fix explains the ownership path that kept the object alive and shows that the same path or type disappears after the patch.

Capture

Prefer capturing from the simulator already used for the reproduction. Resolve the simulator UDID and app bundle identifier, then capture the running app:

SKILL_DIR="<absolute path to this loaded skill folder>"
SIM="<simulator-udid>"
BUNDLE_ID="<app.bundle.identifier>"
MEMGRAPH_DIR="$(mktemp -d "${TMPDIR:-/tmp}/codex-ios-memgraph.XXXXXX")"

"$SKILL_DIR/scripts/capture_sim_memgraph.sh" \
  --udid "$SIM" \
  --bundle-id "$BUNDLE_ID" \
  --out-dir "$MEMGRAPH_DIR"

Do not derive SKILL_DIR from the target app repo's pwd; installed plugins usually live outside the app being debugged. Store captures in a run-specific temp or user-chosen folder, not under SKILL_DIR.

If the process cannot be found, confirm the bundle identifier and use xcrun simctl spawn "$SIM" launchctl list to inspect running labels.

Summarize

Summarize an existing memgraph:

"$SKILL_DIR/scripts/summarize_memgraph_leaks.py" \
  /path/to/app.memgraph \
  --trace-limit 5 \
  --out /path/to/leak-summary.md

Use --trace-limit sparingly. Trace trees are useful root-cause evidence, but large memgraphs can produce noisy output. If a trace tree says Found 0 roots referencing, treat it as an unreachable/self-retained leak candidate and use the summary's grouped leak tree or leaks --groupByType <file.memgraph> to identify the retained fields and payload chain.

Root Cause Rules

  • Identify the first app-owned leaked type in the leak output or trace.
  • Determine the intended lifetime: process, session, account, view, request, or task.
  • Treat lazy or deferred allocation as a scope reduction, not a leak fix, unless the original eager allocation itself violated the intended lifetime.
  • Prove retain-cycle claims with either a traceTree ownership path or an isolated reproduction.
  • For unreachable/self-cycle leaks, traceTree may have no root path; use leaks --groupByType plus source verification to find the self-retaining edge.
  • Do not claim success just because total leak count went down; prove the specific type or path disappeared.
  • Separate real root-cause branches from candidate/noise branches.
  • Prefer deleting the retaining edge over adding broad cleanup code.

Report

A useful leak report includes:

  • the exact flow and simulator/app build
  • the memgraph and summary paths
  • app-owned leaked types and counts
  • at least one ownership path, or grouped leak tree evidence when the object is unreachable from roots
  • the smallest proposed or applied retaining-edge fix
  • before/after evidence when a fix was made

If the memgraph shows only framework/runtime noise, say that and recommend the next narrower capture rather than inventing an app leak.

Related skills

FAQ

What does ios-memgraph-leaks produce?

Simulator memgraph captures, leak summaries, ownership traces, and before-after leak count proof.

When should I use ios-memgraph-leaks?

When proving iOS simulator memory leaks and validating the smallest retaining-edge fix.

Is ios-memgraph-leaks safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.