Skip to content
Back to skills

Find INetworkSystem PollSocket Linux

ASecurity

Agent fallback for INetworkSystem_PollSocket-linux (auto-generated, category: vfunc). Locate INetworkSystem::PollSocket in the CS2 engine module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: INetworkSystem_PollSocket-linux, INetworkSystem::PollSocket

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 27, 2026
databasesgo

Works with

  • mcp

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add mrc4tt/CS2_VibeSignatures --skill find-INetworkSystem_PollSocket-linux --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Find INetworkSystem PollSocket Linux?

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

Security grade badge for Find INetworkSystem PollSocket Linux
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mrc4tt-find-inetworksystem-pollsocket-linux/badge)](https://www.skillsdirectory.com/skills/mrc4tt-find-inetworksystem-pollsocket-linux)

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

Download with Pro
SKILL.md
---
name: find-INetworkSystem_PollSocket-linux
description: |
  Agent fallback for INetworkSystem_PollSocket-linux (auto-generated, category: vfunc). Locate
  INetworkSystem::PollSocket in the CS2 engine module via IDA Pro MCP and emit a fresh,
  minimal-unique artifact. The deterministic preprocessor could not resolve this
  symbol on the current gamever - your job is the re-sign.
  Trigger: INetworkSystem_PollSocket-linux, INetworkSystem::PollSocket
disable-model-invocation: true
---

# Find INetworkSystem_PollSocket-linux

Target: `INetworkSystem::PollSocket` (vfunc) in the module loaded in THIS session.

> The old artifact/preprocessor anchors no longer match this build. Use anchors
> only to *locate* candidates; derive the artifact from the ACTUAL bytes you read.
> Produce ONLY this session's platform output. NEVER open another binary.

## Method

Resolve the owning class vtable via RTTI (typeinfo-name string -> _ZTI object
-> vtable). Identify the slot by xrefs from expected call sites. Slots commonly
differ between platforms - never assume identical indices.

## Mandatory self-check before emitting

The pipeline re-reads the bytes at your `func_va` and regenerates `func_sig` from
them - a mismatch aborts the run. Therefore: read the real bytes via IDA MCP,
derive the artifact FROM those bytes (wildcard relocated operands as `??`), start
at the TRUE function head, and only then write the YAML. A mismatch is always a
bug in YOUR output.

## Output schema (STRICT)

Write `INetworkSystem_PollSocket.{platform}.yaml` with EXACTLY these fields:

```yaml
func_name: <TASK>
func_va: "<hex virtual address>"
func_rva: "<hex rva>"
func_size: "<hex size>"
vtable_name: <owning class RTTI name>
vfunc_offset: "<hex vtable byte offset>"
vfunc_index: <decimal slot index>
```
NEVER include func_sig.

## Verification

1. Decompile and confirm the behavior matches the symbol's semantics.
2. Uniqueness: the pattern must match exactly ONE location in the loaded binary.
3. If no candidate can be confirmed, report the shortlist - a skipped symbol is
   safer than a wrong signature.

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.

View all in databases →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.