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/batteryshark/rekit/macho-analyzenpx skills add batteryshark/rekit --skill macho-analyzegit clone --depth 1 https://github.com/batteryshark/rekitWrote 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/skills/batteryshark/rekit/macho-analyze)<a href="https://agentmods.dev/skills/batteryshark/rekit/macho-analyze"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/macho-analyze.svg" alt="Measured on agentmods" 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.00080 | $0.00551 |
| Opus 5 | $0.00040 | $0.00275 |
| Sonnet 5 | $0.00016 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
macho-analyze 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 5d 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
Mach-O Binary Analyzer
Static triage of Mach-O binaries (macOS/iOS executables, .dylib, bundles, kexts)
with macholib.
When to use
You have a macOS/iOS binary and want a fast read on what it is and whether it looks
suspicious — without running it. This completes the PE/ELF/Mach-O triage trio and
emits BINARY.* atoms for downstream analysis.
What it reports
Per architecture slice (Mach-O can be fat/universal):
- Header — CPU/arch, file type (EXECUTE/DYLIB/BUNDLE/KEXT…), PIE (
BINARY.NO_PIE). - Linked dylibs — every
LC_LOAD_DYLIB, classified for network/crypto frameworks (BINARY.INTERESTING_LINK). - RPATH —
LC_RPATHentries (@rpathdylib-hijack surface) →BINARY.RPATH. - Signature —
LC_CODE_SIGNATUREpresence →BINARY.NO_SIGNATUREwhen absent. - Encryption —
LC_ENCRYPTION_INFOwithcryptidset (protector/DRM, the Mach-O packing tell) →BINARY.ENCRYPTED.
Strictly static — parses load commands via macholib and never loads, maps, or executes the binary. Safe on hostile files.
Usage
rekit run macho-analyze ./suspicious.dylib
rekit run macho-analyze /path/to/app.app/Contents/MacOS/app --format json
Non-Mach-O input fails honestly ({"ok": false, "error": "not a valid Mach-O: …"}).
Prerequisites
- python3 ≥ 3.8 — macholib is installed under
scripts/site(pure-python), so no network/install at analysis time.
Rebuilding
scripts/site is populated from the pinned scripts/requirements.txt by
scripts/build.sh (uv pip install --target, build time only).
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.
- 5d ago First seen · 50 lines · 80 tokens per session scan A 23083393b1aa
macho-analyze is a skill published in the GitHub repository batteryshark/rekit (10 stars, last pushed 27d ago), licensed Apache-2.0. It adds 80 tokens to every session and 551 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…