write-structoffset-as-yaml
Write struct member offset analysis results as YAML file beside the binary using IDA Pro MCP. Use this skill after identifying a struct member offset and optionally generating a signature for it to persist the results in a standardized YAML format.
v2026.11.13-dcf20203 installazioni+3 in 7 giorni67 StelleMITsincronizzato 11 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install hlnd2t/write-structoffset-as-yamlScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoa7737107…30fe1c15
a773710711c9…7ac930fe1c151 file · 2.7 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/write-structoffset-as-yaml@dcf2020
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Persist a single struct member offset analysis result to a YAML file beside the binary using IDA Pro MCP.
Prerequisites
Before using this skill, you should have:
- Identified the struct name and member name
- Determined the member offset (and optionally size)
- Generated a unique signature using
/generate-signature-for-structoffset - An IDA Pro MCP session, resolved per mcp-ida-session.md:
idb_list→idb_open(script fallback only if the endpoint is unreachable). Honor its IDB save discipline — an idle-TTL self-exit does not save.
Required Parameters
| Parameter | Description | Example |
|---|---|---|
struct_name |
Name of the struct/class | CBaseEntity |
member_name |
Name of the struct member | m_skeletonInstance |
offset |
Hex offset of the member from struct start | 0x278 |
Optional Parameters
| Parameter | Description | Example |
|---|---|---|
size |
Size of the member in bytes (use None to omit) |
8 |
artifact_name |
Stable caller-provided filename stem; defaults to <struct_name>_<member_name>. Honor the finder's OUTPUT_NAME_MAP key even when the member name was corrected. |
CEntitySystem_m_bEnableAutoDeletionExecution |
offset_sig |
Unique byte signature locating an instruction that contains the offset (use None to omit) |
8B 93 E0 04 00 00 |
offset_sig_disp |
Byte displacement from signature start to the target instruction. 0 or None means signature starts at the target instruction. Non-zero means backward expansion was used by /generate-signature-for-structoffset. (use None to omit) |
8 |
Method
mcp__ida-pro-mcp__py_eval code="""
import idaapi
import os
import yaml
# === REQUIRED: Replace these values ===
struct_name = "<struct_name>" # e.g., "CBaseEntity"
member_name = "<member_name>" # e.g., "m_skeletonInstance"
artifact_name = f"{struct_name}_{member_name}" # Override with the expected legacy artifact stem if different.
offset = <offset> # e.g., 0x278
# ======================================
# === OPTIONAL: Set to None to omit from output ===
size = <size> # e.g., 8 or None
offset_sig = <offset_sig> # e.g., "8B 93 E0 04 00 00" or None
offset_sig_disp = <offset_sig_disp> # e.g., 8 or None (0 also omitted)
# =================================================
# Get binary path and determine platform
input_file = idaapi.get_input_file_path()
dir_path = os.environ.get('CS2VIBE_ARTIFACT_DIR') or os.path.dirname(input_file)
if input_file.endswith('.dll'):
platform = 'windows'
else:
platform = 'linux'
# Build data dictionary conditionally
data = {}
data['struct_name'] = struct_name
data['member_name'] = member_name
data['offset'] = hex(offset)
if size is not None and size > 0:
data['size'] = size
if offset_sig is not None:
data['offset_sig'] = offset_sig
if offset_sig_disp is not None and offset_sig_disp > 0:
data['offset_sig_disp'] = offset_sig_disp
yaml_path = os.path.join(dir_path, f"{artifact_name}.{platform}.yaml")
with open(yaml_path, 'w', encoding='utf-8') as f:
yaml.dump(data, f, default_flow_style=False, sort_keys=False, allow_unicode=True)
print(f"Written to: {yaml_path}")
"""Output File Naming Convention
The output YAML filename follows this pattern:
<artifact_name>.<platform>.yaml(defaults to<struct_name>_<member_name>)
Examples:
server.dll→CBaseEntity_m_skeletonInstance.windows.yamllibserver.so/libserver.so→CBaseEntity_m_skeletonInstance.linux.yaml
Output YAML Format
Full output (with size, offset_sig, and offset_sig_disp provided):
struct_name: CBaseEntity
member_name: m_skeletonInstance
offset: 0x278
size: 8
offset_sig: FF 50 ?? 48 85 C0 74 ?? 48 8B 80 A0 03 00 00 48 83 C4 28 C3
offset_sig_disp: 8Output without backward expansion (offset_sig_disp is 0 or omitted):
struct_name: CBaseEntity
member_name: m_skeletonInstance
offset: 0x278
size: 8
offset_sig: 8B 93 78 02 00 00Minimal output (with size=None, offset_sig=None):
struct_name: CBaseEntity
member_name: m_skeletonInstance
offset: 0x278Each field:
struct_name- Name of the struct/classmember_name- Name of the struct memberoffset- Hex offset from struct startsize(optional) - Size in bytesoffset_sig(optional) - Unique byte signature of an instruction containing the offset (e.g.,8B 93 E0 04 00 00formov edx, [rbx+4E0h])offset_sig_disp(optional) - Byte displacement from signature start to the target instruction. Only present when non-zero (backward expansion was used). Runtime: scan foroffset_sig, then addoffset_sig_dispto get the target instruction address.
Platform Detection
The skill automatically detects the platform based on file extension:
.dll→ Windows.so→ Linux
Example Usage
With all parameters
struct_name = "CBaseEntity"
member_name = "m_skeletonInstance"
offset = 0x278
size = 8
offset_sig = "8B 93 78 02 00 00"
offset_sig_disp = NoneWith backward-expanded signature
struct_name = "CSkeletonInstance"
member_name = "m_animationController"
offset = 0x3A0
size = 8
offset_sig = "FF 50 40 48 85 C0 74 0C 48 8B 80 A0 03 00 00 48 83 C4 28 C3"
offset_sig_disp = 8Without optional parameters
struct_name = "CBaseEntity"
member_name = "m_skeletonInstance"
offset = 0x278
size = None
offset_sig = None
offset_sig_disp = NoneWith only size
struct_name = "CBaseEntity"
member_name = "m_iHealth"
offset = 0x408
size = 4
offset_sig = NoneWith only signature
struct_name = "CBaseEntity"
member_name = "m_nActualMoveType"
offset = 0x4E0
size = None
offset_sig = "8B 93 E0 04 00 00"Trusted finalization
This writer produces a semantic YAML payload at the caller-provided expected artifact path. It does not own final field ordering, scalar spelling, encoding, or line endings. After runtime validation, the trusted analyzer rewrites every successful preprocessor or Agent output through the Source2 central canonicalizer; that canonical rewrite is the only byte-level trust boundary.
Notes
- All offsets are written in hexadecimal format with lowercase
0xprefix - The YAML file is written to the same directory as the input binary
- When
sizeisNoneor0, thesizefield is omitted from the output entirely - When
offset_sigisNone, theoffset_sigfield is omitted from the output entirely - When
offset_sig_dispisNoneor0, theoffset_sig_dispfield is omitted from the output entirely (signature starts at the target instruction) offset_sigshould be a signature generated by/generate-signature-for-structoffsetoffset_sig_dispis the byte displacement from signature start to the target instruction, only needed when backward expansion was used
File di questa versione
- SKILL.md7.2 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | Sì | Sì |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | Sì | Sì |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-dcf2020 | 13 nov 2026 | dcf2020 | a7737107 | Firmata | – |
Altro da HLND2T
Tutto da questo editoreAltro in Reverse engineering e fuzzing
Vai alla categoriaChiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login