Skip to content
Back to skills

2490 Offset Sig 8f10b3f6

ASecurity

`offset_sig` is the relocation signature used to recover struct-member offsets across versions.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
ai-agentsgo

Works with

  • mcp

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2490-offset_sig_8f10b3f6 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2490 Offset Sig 8f10b3f6?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2490 Offset Sig 8f10b3f6
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2490-offset-sig-8f10b3f6/badge)](https://www.skillsdirectory.com/skills/tools-only-2490-offset-sig-8f10b3f6)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# offset_sig

## Overview
`offset_sig` is the relocation signature used to recover struct-member offsets across versions.

## Field Context
- Related YAML fields: `struct_name`, `member_name`, `offset`, `size`, `offset_sig` (optional `offset_sig_disp`).

## Generation Principle
- In this repository, authoring usually follows the struct-offset signature workflow (`.claude/skills/generate-signature-for-structoffset/SKILL.md`).
- Signature is built near an instruction that encodes/uses the target member offset.
- Volatile bytes are wildcarded (`??`) to improve cross-version robustness.
- Observed outputs generally use forward anchoring (signature starts at target instruction, `offset_sig_disp` omitted/0).
- Acceptance goal: unique matching plus reliable offset re-derivation.

## Usage Method
- In `preprocess_struct_offset_sig_via_mcp`, old `offset_sig` is reused to recover the new `offset`.
- Flow:
  1. Load `struct_name`, `member_name`, `offset_sig`, optional `offset_sig_disp`, optional `size`.
  2. Unique-match `offset_sig` -> `sig_addr`.
  3. Compute instruction address: `inst_addr = sig_addr + offset_sig_disp` (default 0).
  4. Decode instruction and inspect operand positions (`offb/offo`) and candidate sizes.
  5. Extract displacement/immediate candidates; prefer candidates matching old offset when available.
  6. Emit new YAML with updated `offset`, carrying `offset_sig` and optional metadata.

## Practical Notes
- Multi-hit `offset_sig` is rejected.
- Non-zero `offset_sig_disp` means signature starts before target instruction.
- `offset` may change across versions; `offset_sig` should remain stable enough to re-derive it.
- Weak signatures (too short/too wildcarded) reduce long-term reliability.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…