Home / 2389-research / binary-re · GitHub

binary-re:triage SKILL.md skillA

binary-re:triage from 2389-research/binary-re is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add 2389-research/binary-re/binary-re:triage@git:20260706.1bbfa9b

Pins git:20260706.1bbfa9b in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: 2389-research/binary-re
Path: skills/triage/SKILL.md
Versions recorded: 4
Latest version: git:20260706.1bbfa9b, committed Jul 6, 2026
First version recorded: Jan 6, 2026
Size: 6,696 bytes
Repository stars: 22
License: MIT

Fingerprints unknown binaries using rabin2 — detects architecture (ARM, x86, MIPS), ABI, libc, dependencies, and strings of interest. Use when first encountering an unknown binary, ELF file, or firmware blob, or when you need architecture or ABI information before committing to deeper analysis.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Binary Triage (Phase 1)

## Purpose

Quick fingerprinting to establish baseline facts before deeper analysis. Runs in seconds, not minutes.

## When to Use

- First contact with an unknown binary
- Need architecture/ABI info for tool selection
- Quick capability assessment
- Before committing to expensive analysis

## Key Principle

**Gather facts fast, defer analysis.**

This phase identifies WHAT the binary is, not HOW it works.

## Triage Sequence

### Step 1: File Identification

```bash
# Basic identification
file binary

# Expected output patterns:
# ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3
# ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1
```

**Extract:**
- Architecture (ARM, ARM64, x86_64, MIPS)
- Bit width (32/64)
- Endianness (LSB/MSB)
- Link type (static/dynamic)
- Interpreter path (libc indicator)

### Step 2: Structured Metadata (rabin2)

```bash
# All metadata as JSON
rabin2 -q -j -I binary | jq .

# Key fields:
# .arch     - "arm", "x86", "mips"
# .bits     - 32 or 64
# .endian   - "little" or "big"
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add 2389-research/binary-re/binary-re:triage@sha256:bde56718dcaf3db5

The line at the top of this page pins the label git:20260706.1bbfa9b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_nilehim3rhwbc646.svg)](https://markdownregistry.com/a/art_nilehim3rhwbc646)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Jan 6, 2026 and Jul 6, 2026, about one every 60 days.

version	committed	commit	size	audit
git:20260706.1bbfa9b latest	2026-07-06	1bbfa9b	6,696 B	A	view · diff
git:20260106.49edd78	2026-01-06	49edd78	6,734 B	A	view · diff
git:20260106.3ea64f1	2026-01-06	3ea64f1	6,734 B	A	view · diff
git:20260106.b6bcfb3	2026-01-06	b6bcfb3	6,540 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6696 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

2389-research/binary-re · 22 stars · license MIT · pushed 2026-09-25 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_nilehim3rhwbc646
GET https://markdownregistry.com/api/v1/resolve?ref=2389-research/binary-re/binary-re:triage
GET https://markdownregistry.com/api/v1/blob/bde56718dcaf3db538d90bdc34af6187e9c4f86dcdcbb4426fb63017bfcceeb5

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.