write-vtable-as-yaml
Write vtable analysis results as YAML file beside the binary using IDA Pro MCP. Use this skill after locating a vtable to persist the results in a standardized YAML format.
v2026.11.13-dcf20204 installs+4 in 7 days67 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install hlnd2t/write-vtable-as-yamlWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package05dfbb5d…32bef1db
05dfbb5df86d…e54232bef1db1 file · 2.5 KBScanLowno findings
Sourcegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/write-vtable-as-yaml@dcf2020
On this page
Persist vtable analysis results to a YAML file beside the binary using IDA Pro MCP.
Prerequisites
Before using this skill, you should have:
- Located the target vtable address
- Identified the class name for the vtable
- 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 |
|---|---|---|
vtable_class |
Class name for the vtable | CSource2Server |
vtable_va |
Virtual address of the vtable | 0x182B8D9D8 |
Optional Parameters
| Parameter | Description | Example |
|---|---|---|
vtable_symbol |
The IDA symbol name for the vtable | "??_7CBaseEntity@@6B@" |
Method
mcp__ida-pro-mcp__py_eval code="""
import idaapi
import ida_bytes
import ida_name
import os
import yaml
# === REQUIRED: Replace these values ===
vtable_class = "<vtable_class>" # e.g., "CBaseEntity"
vtable_va = <vtable_va> # e.g., 0x182B8D9D8
# ======================================
# === OPTIONAL: Replace these values ===
vtable_symbol = "<vtable_symbol>" # e.g., "??_7CBaseEntity@@6B@" or "_ZTV11CBaseEntity + 0x10" or "off_180XXXXXX"
# ======================================
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'
image_base = idaapi.get_imagebase()
else:
platform = 'linux'
image_base = 0x0
vtable_rva = vtable_va - image_base
# Handle Linux vtables (skip RTTI metadata)
vtable_name = ida_name.get_name(vtable_va) or ""
if vtable_name.startswith("_ZTV"):
vtable_va = vtable_va + 0x10
vtable_rva = vtable_va - image_base
# Determine pointer size and count virtual functions
ptr_size = 8 if idaapi.inf_is_64bit() else 4
vtable_entries = []
for i in range(1000):
if ptr_size == 8:
ptr_value = ida_bytes.get_qword(vtable_va + i * ptr_size)
else:
ptr_value = ida_bytes.get_dword(vtable_va + i * ptr_size)
if ptr_value == 0 or ptr_value == 0xFFFFFFFFFFFFFFFF:
break
func = idaapi.get_func(ptr_value)
if func is None:
flags = ida_bytes.get_full_flags(ptr_value)
if not ida_bytes.is_code(flags):
break
vtable_entries.append(ptr_value)
count = len(vtable_entries)
vtable_size = count * ptr_size
# Build YAML data structure
yaml_data = {
'vtable_class': vtable_class,
'vtable_symbol': vtable_symbol,
'vtable_va': hex(vtable_va),
'vtable_rva': hex(vtable_rva),
'vtable_size': hex(vtable_size),
'vtable_numvfunc': count,
'vtable_entries': {i: hex(entry) for i, entry in enumerate(vtable_entries)}
}
yaml_path = os.path.join(dir_path, f"{vtable_class}_vtable.{platform}.yaml")
with open(yaml_path, 'w', encoding='utf-8') as f:
yaml.dump(yaml_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:
<vtable_class>_vtable.<platform>.yaml
Examples:
server.dll→CSource2Server_vtable.windows.yamllibserver.so/libserver.so→CSource2Server_vtable.linux.yaml
Output YAML Format
CSource2Server_vtable.windows.yaml - Example for CSource2Server vtable on Windows:
vtable_class: CSource2Server
vtable_symbol: off_180XXXXXX # Symbol in IDA to CSource2Server's vtable
vtable_va: 0x182B8D9D8 # Virtual address - changes with game updates
vtable_rva: 0x2B8D9D8 # Relative virtual address (VA - image base) - changes with game updates
vtable_size: 0x2D8 # VTable size in bytes - changes with game updates
vtable_numvfunc: 97 # Number of virtual functions - changes with game updates
vtable_entries: # Every virtual functions starting from vtable[0]
0: 0x180C87B20 # vtable[0] - changes with game updates
1: 0x180C87FA0 # vtable[1] - changes with game updates
2: 0x180C87FF0 # vtable[2] - changes with game updatesCSource2Server_vtable.linux.yaml - Example for CSource2Server vtable on linux:
vtable_class: CSource2Server
vtable_symbol: _ZTV14CSource2Server + 0x10 # Symbol in IDA to CSource2Server's vtable
vtable_va: '0x2261dd8' # Virtual address - changes with game updates
vtable_rva: '0x2261dd8' # Relative virtual address (VA - image base) - changes with game updates
vtable_size: '0x310' # VTable size in bytes - changes with game updates
vtable_numvfunc: 98 # Number of virtual functions - changes with game updates
vtable_entries: # Every virtual functions starting from vtable[0]
0: '0x16ea780' # vtable[0] - changes with game updates
1: '0x16e9b50' # vtable[1] - changes with game updates
2: '0x16e3270' # vtable[2] - changes with game updatesPlatform Detection
The skill automatically detects the platform based on file extension:
.dll→ Windows (usesidaapi.get_imagebase()for image base).so→ Linux (uses0x0as image base, skips RTTI metadata for_ZTVprefixed vtables)
Linux VTable Handling
For Linux binaries, vtables with _ZTV prefix (mangled vtable names) have RTTI metadata at the beginning:
- Offset 0x00: offset to top
- Offset 0x08: RTTI pointer
- Offset 0x10: First virtual function pointer
The skill automatically skips this metadata when counting virtual functions.
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 values marked "changes with game updates" should be regenerated when analyzing new binary versions
- The YAML file is written to the same directory as the input binary
- vtable_size is automatically calculated as
vtable_numvfunc * pointer_size - vtable_rva is automatically calculated as
vtable_va - image_base
Files in this version
- SKILL.md6.5 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | Yes | Yes |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-dcf2020 | Nov 13, 2026 | dcf2020 | 05dfbb5d | Signed | – |
More from HLND2T
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login