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 skills add HexRaysSA/claude-marketplace --skill ida-domain-scriptinggit clone --depth 1 https://github.com/HexRaysSA/claude-marketplaceWrote 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/hexrayssa/claude-marketplace/ida-domain-scripting)<a href="https://agentmods.dev/skills/hexrayssa/claude-marketplace/ida-domain-scripting"><img src="https://agentmods.dev/badge/skills/hexrayssa/claude-marketplace/ida-domain-scripting/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.
<a href="https://agentmods.dev/skills/hexrayssa/claude-marketplace/ida-domain-scripting"><img src="https://agentmods.dev/badge/skills/hexrayssa/claude-marketplace/ida-domain-scripting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00069 | $0.02654 |
| Opus 5 | $0.00034 | $0.01327 |
| Sonnet 5 | $0.00014 | $0.00531 |
| Haiku 4.5 | $0.00007 | $0.00265 |
Grade A, and why
ida-domain-scripting 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT - Path Resolution:
This skill can be installed in different locations. Before executing any commands, determine the skill directory based
on where you loaded this SKILL.md file, and use that path in all commands below. Replace $SKILL_DIR with the actual
discovered path.
Common installation paths:
- Project-specific:
<project>/.claude/skills/ida-domain-scripting - Manual global:
~/.claude/skills/ida-domain-scripting
IDA Domain Scripting
General-purpose binary analysis skill. I'll write custom IDAPython code for any reverse engineering task you request and execute it via the universal executor.
CRITICAL WORKFLOW - Follow these steps in order:
-
Create a work dir in /tmp with timestamp - NEVER write scripts to skill directory; always create a workdir
/tmp/ida-domain-YYYYMMDD_HHMMSS_ffffff-<name>with microseconds for uniqueness (e.g.,/tmp/ida-domain-20260109_143052_847291-list-functions). Generate timestamp with:datetime.now(). strftime ('%Y%m%d_%H%M%S_%f'). This will always be referenced as <work_dir> -
Check API_REFERENCE.md exists - Always check that $SKILL_DIR/API_REFERENCE.md exists. Inform the user to run the bootstrap if not.
-
Execute from skill directory - Always run:
cd $SKILL_DIR && uv run python run.py <work_dir>/script.py -f <binary> -
Ask before saving - Scripts that modify the database require explicit user confirmation before using
--save
How It Works
- You describe what you want to analyze/extract
- I write custom IDA Domain API code in
<work_dir>/script.py(timestamped with microseconds for parallel execution) - I execute it via:
cd $SKILL_DIR && uv run python run.py <work_dir>/script.py -f <binary> - Results displayed in real-time
- Script files auto-cleaned from /tmp by your OS
Setup (First Time)
cd $SKILL_DIR && uv run python setup.py
This clones ida-domain from GitHub and installs dependencies. Only needed once.
Using a specific version:
What ships with it
4 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.
- 10d ago First seen · 351 lines · 69 tokens per session scan A 0d82cc8dc638
ida-domain-scripting is a skill published in the GitHub repository HexRaysSA/claude-marketplace (119 stars, last pushed 13d ago), licensed MIT. It adds 69 tokens to every session and 2,654 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
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…
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.
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.
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.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.