Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/hlnd2t/cs2_vibesignatures/write-structoffset-as-yamlnpx skills add HLND2T/CS2_VibeSignatures --skill write-structoffset-as-yamlgit clone --depth 1 https://github.com/HLND2T/CS2_VibeSignaturesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/write-structoffset-as-yaml)<a href="https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/write-structoffset-as-yaml"><img src="https://agentmods.dev/badge/skills/hlnd2t/cs2_vibesignatures/write-structoffset-as-yaml.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00052 | $0.01693 |
| Opus 5 | $0.00026 | $0.00847 |
| Sonnet 5 | $0.00010 | $0.00339 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
write-structoffset-as-yaml scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Struct Offset as YAML
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
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 |
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"
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.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"{struct_name}_{member_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}")
"""
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 200 lines · 52 tokens per session scan A 49dc3b768aff
write-structoffset-as-yaml is a skill published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,693 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…