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 skills/robdel12/orbitdock/orbitdock-memory-profilingnpx skills add Robdel12/OrbitDock --skill orbitdock-memory-profilinggit clone --depth 1 https://github.com/Robdel12/OrbitDockWhat 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.00060 | $0.00504 |
| Opus 5 | $0.00030 | $0.00252 |
| Sonnet 5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
orbitdock-memory-profiling 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.
What it actually says
OrbitDock Memory Profiling
Overview
Capture reproducible OrbitDock memory artifacts from the command line, then map hotspots back to likely UI or rendering causes.
Workflow
- Identify the target process.
- Capture baseline snapshots.
- Reproduce the issue.
- Capture post-repro snapshots.
- Compare outputs and form hypotheses.
Prefer using scripts/capture_memory_profile.sh for consistency.
Run The Script
Run a full capture for the latest OrbitDock process:
scripts/capture_memory_profile.sh
Run a targeted capture:
scripts/capture_memory_profile.sh \
--pid 9718 \
--sample-seconds 5 \
--trace-seconds 10 \
--out-dir /tmp/orbitdock-profile
Manual Commands
Use these directly when you need finer control:
pgrep -lf OrbitDock
ps -o pid,ppid,rss,vsz,%mem,etime,command -p <PID>
vmmap -summary <PID>
sample <PID> 5 1
xctrace record --template 'Allocations' --attach <PID> --time-limit 10s --output /tmp/orbitdock-alloc.trace
xctrace export --input /tmp/orbitdock-alloc.trace --toc
Permission Handling
If vmmap, sample, leaks, or xctrace fails with permission errors, request elevated execution and rerun the same command.
Interpretation Guide
Read references/interpretation.md for quick heuristics on:
- CoreAnimation and image-backed growth
- MALLOC_SMALL and fragmentation signals
- Peak vs current footprint interpretation
- Stack patterns that implicate rendering, focus rings, or image decode paths
Output Expectations
The capture script writes:
ps.txtvmmap-summary.txtsample.txtallocations.traceandxctrace-toc.xml(if tracing enabled)capture-summary.txt
Use these artifacts to compare before/after repro windows and support fixes with evidence.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 68 lines · 60 tokens per session scan A 594b13432eb2
orbitdock-memory-profiling is a skill published in the GitHub repository Robdel12/OrbitDock (95 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 504 once invoked, about $0.0003 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 skills, from other repositories
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
swiftui-pro
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
onlyswitch-deeplink
Invoke OnlySwitch built-in switches or buttons via deeplink. Use when the user asks to toggle or trigger an OnlySwitch action (e.g. empty trash, keep awake, dark mode, mute, hide desktop, clear clipboard, eject discs, Xcode derived data, and any other built-in switch or button). Resolve the request to the correct…
awesome-swift-macos-apps-docs
Use when adding, updating, or validating app entries in the awesome-swift-macos-apps repository, especially when maintaining both README.md and README.zh.md with concise one-sentence descriptions, correct category placement, and consistent bilingual formatting.