agentleFS
QiuChenlyQiuChenly/ida-pro-mcp-enhancement/skills/idapython/SKILL.md

idapython

Skill554 starsChanged 8 months agoMITView on GitHub

IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida_* modules (50+), idautils iterators, and common patterns.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use modern ida_* modules. Avoid legacy idc module.

    line 8
  2. Very specific:

    Wait for analysis: Call ida_auto.auto_wait() before reading results

    line 133
  3. Very specific:

    64-bit addresses: Always assume ea_t can be 64-bit

    line 135

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IDAPython

Use modern ida_* modules. Avoid legacy idc module.

Module Router

TaskModuleKey Items
Bytes/memoryida_bytesget_bytes, patch_bytes, get_flags, create_*
Functionsida_funcsfunc_t, get_func, add_func, get_func_name
Namesida_nameset_name, get_name, demangle_name
Typesida_typeinftinfo_t, apply_tinfo, parse_decl
Decompilerida_hexraysdecompile, cfunc_t, lvar_t, ctree visitor
Segmentsida_segmentsegment_t, getseg, add_segm
Xrefsida_xrefxrefblk_t, add_cref, add_dref
Instructionsida_uainsn_t, op_t, decode_insn
Stack framesida_frameget_frame, define_stkvar
IterationidautilsFunctions(), Heads(), XrefsTo(), Strings()
UI/dialogsida_kernwinmsg, ask_*, jumpto, Choose
Database infoida_idainf_get_*, inf_is_64bit()
Analysisida_autoauto_wait, plan_and_wait
Flow graphsida_gdlFlowChart, BasicBlock
Register trackingida_regfinderfind_reg_value, reg_value_info_t

Core Patterns

Iterate functions

for ea in idautils.Functions():
    name = ida_funcs.get_func_name(ea)
    func = ida_funcs.get_func(ea)

Iterate instructions in function

for head in idautils.FuncItems(func_ea):
    insn = ida_ua.insn_t()
    if ida_ua.decode_insn(insn, head):
        print(f"{head:#x}: {insn.itype}")

Cross-references

for xref in idautils.XrefsTo(ea):
    print(f"{xref.frm:#x} -> {xref.to:#x} type={xref.type}")

Read/write bytes

data = ida_bytes.get_bytes(ea, size)
ida_bytes.patch_bytes(ea, b"\x90\x90")

Names

name = ida_name.get_name(ea)
ida_name.set_name(ea, "new_name", ida_name.SN_NOCHECK)

Decompile function

cfunc = ida_hexrays.decompile(ea)
if cfunc:
    print(cfunc)  # pseudocode
    for lvar in cfunc.lvars:
        print(f"{lvar.name}: {lvar.type()}")

Walk ctree (decompiled AST)

class MyVisitor(ida_hexrays.ctree_visitor_t):
    def visit_expr(self, e):
        if e.op == ida_hexrays.cot_call:
            print(f"Call at {e.ea:#x}")
        return 0

cfunc = ida_hexrays.decompile(ea)
MyVisitor().apply_to(cfunc.body, None)

Apply type

tif = ida_typeinf.tinfo_t()
if ida_typeinf.parse_decl(tif, None, "int (*)(char *, int)", 0):
    ida_typeinf.apply_tinfo(ea, tif, ida_typeinf.TINFO_DEFINITE)

Create structure

udt = ida_typeinf.udt_type_data_t()
m = ida_typeinf.udm_t()
m.name = "field1"
m.type = ida_typeinf.tinfo_t(ida_typeinf.BTF_INT32)
m.offset = 0
m.size = 4
udt.push_back(m)
tif = ida_typeinf.tinfo_t()
tif.create_udt(udt, ida_typeinf.BTF_STRUCT)
tif.set_named_type(ida_typeinf.get_idati(), "MyStruct")

Strings list

for s in idautils.Strings():
    print(f"{s.ea:#x}: {str(s)}")

Wait for analysis

ida_auto.auto_wait()  # Block until autoanalysis completes

Key Constants

ConstantValue/Use
BADADDRInvalid address sentinel
ida_name.SN_NOCHECKSkip name validation
ida_typeinf.TINFO_DEFINITEForce type application
o_reg, o_mem, o_imm, o_displ, o_nearOperand types
dt_byte, dt_word, dt_dword, dt_qwordData types
fl_CF, fl_CN, fl_JF, fl_JN, fl_FCode xref types
dr_R, dr_W, dr_OData xref types

Critical Rules

  1. NEVER convert hex/decimal manually — use int_convert MCP tool
  2. Wait for analysis: Call ida_auto.auto_wait() before reading results
  3. Thread safety: IDA SDK calls must run on main thread (use @idasync)
  4. 64-bit addresses: Always assume ea_t can be 64-bit

Anti-Patterns

AvoidDo Instead
idc.* functionsUse ida_* modules
Hardcoded addressesUse names, patterns, or xrefs
Manual hex conversionUse int_convert tool
Blocking main threadUse execute_sync() for long ops
Guessing at typesDerive from disassembly/decompilation

Detailed API Reference

For comprehensive documentation on any module, read docs/<module>.md:

  • High-use: ida_bytes, ida_funcs, ida_hexrays, ida_typeinf, ida_name, idautils
  • Medium-use: ida_segment, ida_xref, ida_ua, ida_frame, ida_kernwin
  • Specialized: ida_dbg (debugger), ida_nalt (netnode storage), ida_regfinder (register tracking)

Full RST sources from hex-rays.com available at docs/<module>.rst.

Download now (ZIP)

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. mrexodia/ida-pro-mcp★ 12k100% same

    Edited · 1

    1. ackwrap/ida-pro-agent★ 552% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.