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/rename-preprocessor-scriptsnpx skills add HLND2T/CS2_VibeSignatures --skill rename-preprocessor-scriptsgit 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/rename-preprocessor-scripts)<a href="https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/rename-preprocessor-scripts"><img src="https://agentmods.dev/badge/skills/hlnd2t/cs2_vibesignatures/rename-preprocessor-scripts.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 | $0.00099 | $0.05245 |
| Opus 5 | $0.00049 | $0.02622 |
| Sonnet 5 | $0.00020 | $0.01049 |
| Haiku 4.5 | $0.00010 | $0.00524 |
Grade A, and why
rename-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 5d 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rename Preprocessor Scripts
Rename a symbol from OldName to NewName across all files in the preprocessor pipeline:
the Python script, configs/<GAMEVER>.yaml, and every per-gamever YAML output file under bin/.
Resolve GAMEVER from the user's explicit request or CS2VIBE_GAMEVER; edit only
configs/$GAMEVER.yaml and stop if it is missing.
When to Use
- A symbol's name changes (e.g. class renamed from
ILoopTypetoCLoopTypeBase) - A naming-convention fix applies to one or more existing preprocessor scripts
- Deinline-fix: a single
find-Xfinder must be split into an inline/noinline chain because a helper that used to be inlined became a separate function (de-inlined) on some build. This skill covers thefind-X-inlinedrename step (Step 1–3 below); the full 3-skill chain recipe lives in create-preprocessor-scripts Pattern M
Inputs
| Field | Description | Example |
|---|---|---|
| Old name | Current symbol name to replace | ILoopType_EngineLoop |
| New name | New symbol name | CLoopTypeBase_EngineLoop |
| Old class (optional) | Old vtable class name, if applicable | ILoopType |
| New class (optional) | New vtable class name, if applicable | CLoopTypeBase |
If only the symbol suffix changes (e.g.
Foo_Bar→Foo_Baz) and the vtable class stays the same, skip the class rename steps below.
Multiple renames at once: run all steps for every symbol in a single pass — batch the
sedcalls with multiple-eflags rather than doing separate passes per symbol.
Step 1: Find All Affected Files
Search for every occurrence of the old name across the entire repo:
grep -r "OldName" --include="*.py" --include="*.yaml" -l
Expected hits fall into these categories:
| File type | Path pattern | What changes |
|---|---|---|
| Preprocessor script | ida_preprocessor_scripts/find-OldName.py |
File renamed + content updated |
| configs/.yaml | configs/<GAMEVER>.yaml |
Skill name, expected_output, skip_if_exists, symbol name + alias |
| Output YAMLs | bin/*/client|engine/OldName.{platform}.yaml |
File renamed + func_name / vtable_name fields |
| Reference YAMLs | ida_preprocessor_scripts/references/**/*.yaml |
File renamed (if named after symbol) or comment strings updated |
| Test files | tests/*.py |
Fixture data, assertions, class/method names updated |
What ships with it
1 file 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.
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.
- 5d ago First seen · 448 lines · 99 tokens per session scan A 9602ac6eac03
rename-preprocessor-scripts is a skill published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 5,245 once invoked, about $0.0005 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…