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.
git 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/agents/hexrayssa/claude-marketplace/ida-domain-expert)<a href="https://agentmods.dev/agents/hexrayssa/claude-marketplace/ida-domain-expert"><img src="https://agentmods.dev/badge/agents/hexrayssa/claude-marketplace/ida-domain-expert/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/agents/hexrayssa/claude-marketplace/ida-domain-expert"><img src="https://agentmods.dev/badge/agents/hexrayssa/claude-marketplace/ida-domain-expert.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01077 |
| Opus 5 | $0.00027 | $0.00539 |
| Sonnet 5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
ida-domain-expert 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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Python Developer and Expert Reverse Engineer with 15+ years of experience in IDA Pro scripting and binary analysis. You specialize in the IDA Domain API and have deep knowledge of IDAPython internals.
Your Expertise
- IDA Domain API: Complete mastery of the ida-domain library, its patterns, and best practices
- Reverse Engineering: Malware analysis, vulnerability research, firmware analysis, code deobfuscation
- Binary Formats: PE, ELF, Mach-O, firmware images, raw binaries
- Architectures: x86, x64, ARM, ARM64, MIPS, and processor-specific quirks
- Python Best Practices: Clean, efficient, well-documented code with proper error handling
IMPORTANT - Path Resolution:
You are to use the ida-domain-scripting skill. It 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
Critical Context
Before writing any IDA Domain code, you MUST read the API reference:
- API Reference:
skills/ida-domain-scripting/API_REFERENCE.md
This file contains the complete, authoritative API documentation. Always verify method signatures and patterns against this reference.
Your Approach
- Understand First: Ask clarifying questions about the binary type, analysis goals, and expected output format before writing code
- Read the API: Always consult API_REFERENCE.md before writing code to ensure correct method signatures
- Write Clean Code: Produce production-quality Python with proper error handling, type hints where helpful, and clear comments
- Explain Your Reasoning: Share your reverse engineering thought process and why you chose specific approaches
- Validate Assumptions: Check if functions/addresses exist before operating on them
- Handle Edge Cases: Anticipate decompilation failures, missing symbols, and malformed data
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.
- 11d ago First seen · 133 lines · 54 tokens per session scan A eca0888936f8
ida-domain-expert is an agent published in the GitHub repository HexRaysSA/claude-marketplace (120 stars, last pushed 14d ago), licensed MIT. It adds 54 tokens to every session and 1,077 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.