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/create-preprocessor-scriptsnpx skills add HLND2T/CS2_VibeSignatures --skill create-preprocessor-scriptsgit clone --depth 1 https://github.com/HLND2T/CS2_VibeSignaturesWhat 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 | $0.00070 | $0.17558 |
| Opus 5 | $0.00035 | $0.08779 |
| Sonnet 5 | $0.00014 | $0.03512 |
| Haiku 4.5 | $0.00007 | $0.01756 |
Grade A, and why
create-preprocessor-scripts 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 2d 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 — 1,099 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Preprocessor Scripts from Scratch
Create an ida_preprocessor_scripts/find-XXXX.py preprocessor script and add the corresponding
configs/<GAMEVER>.yaml entries for a newly requested function, vtable, or struct member offset.
Resolve GAMEVER from the user's explicit request or CS2VIBE_GAMEVER, set the edit target to
configs/$GAMEVER.yaml, and stop if that exact file does not exist. Never edit another version as a fallback.
When to Use
- A GitHub issue or user instruction requests adding support for finding a new function/symbol
- No existing
.claude/skills/find-XXXX/SKILL.mdneeds conversion (for that, useconvert-finder-skill-to-preprocessor-scripts)
Inputs
The user or issue will provide some or all of:
| Field | Description | Example |
|---|---|---|
| Function name(s) | Target symbol(s) to find | CPlayer_MovementServices_PlayWaterStepSound |
| Module | Which DLL/SO the function lives in | server, engine, networksystem, client |
| Category | Symbol type | func, vfunc, structmember, patch, vtable |
| xref_strings | Debug strings for xref-based discovery | "CT_Water.StepLeft" |
| xref_gvs | Global variable VA (e.g. vtable address) to find functions that reference it | vtable VA from SomeClass_vtable.{platform}.yaml |
| xref_funcs | Known callee function name to find its callers | "CPlayerCommandQueue_ctor" |
| Predecessor function | Function to decompile for LLM_DECOMPILE patterns | CBaseEntity_TakeDamageOld |
| VTable class | Class owning the vtable (for vfuncs) | CBasePlayerPawn |
| Desired YAML fields | Which fields the output YAML needs | func_name, func_sig, func_va, func_rva, func_size |
| Dependencies | Input YAMLs this skill depends on | CCSPlayer_MovementServices_vtable.{platform}.yaml |
| Aliases | Alternative names for the symbol | CPlayer_MovementServices::PlayWaterStepSound |
Overview
Twelve preprocessor patterns exist. The discovery method and target type determine which to use:
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 43 B
- references/pattern-A.md 3.2 KB
- references/pattern-B.md 3.5 KB
- references/pattern-C.md 4.5 KB
- references/pattern-D.md 2.0 KB
- references/pattern-E.md 4.1 KB
- references/pattern-F.md 6.4 KB
- references/pattern-G.md 3.0 KB
- references/pattern-H.md 3.7 KB
- references/pattern-I.md 8.7 KB
- references/pattern-J.md 5.2 KB
- references/pattern-L.md 8.4 KB
- references/pattern-M.md 12 KB
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.
- 2d ago First seen · 1,099 lines · 70 tokens per session scan A f389ca240604
create-preprocessor-scripts is a skill published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 17,558 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.