Borrowing it
Nothing to install: this file belongs to HLND2T/CS2_VibeSignatures. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HLND2T/CS2_VibeSignatures/main/.claude/skills/find-CBaseEntity_GetChangeAccessorPathInfo_1/SKILL.mdgit 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/find-cbaseentity_getchangeaccessorpathinfo_1)<a href="https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/find-cbaseentity_getchangeaccessorpathinfo_1"><img src="https://agentmods.dev/badge/skills/hlnd2t/cs2_vibesignatures/find-cbaseentity_getchangeaccessorpathinfo_1/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/find-cbaseentity_getchangeaccessorpathinfo_1"><img src="https://agentmods.dev/badge/skills/hlnd2t/cs2_vibesignatures/find-cbaseentity_getchangeaccessorpathinfo_1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00115 | $0.01725 |
| Opus 5 | $0.00057 | $0.00863 |
| Sonnet 5 | $0.00023 | $0.00345 |
| Haiku 4.5 | $0.00012 | $0.00172 |
Grade A, and why
find-CBaseEntity_GetChangeAccessorPathInfo_1 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 11d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find CBaseEntity_GetChangeAccessorPathInfo_1
Locate CBaseEntity_GetChangeAccessorPathInfo_1 vfunc in CS2 server.dll or libserver.so using IDA Pro MCP tools.
Background
CBaseEntity overrides two separate CEntityInstance interface methods, GetChangeAccessorPathInfo_1 and
GetChangeAccessorPathInfo_2, with byte-for-byte identical implementations (both simply forward to the same
internal lazy-init helper at the same member offset). Because the source bodies are identical, the compiler may
fold both vtable slots onto the exact same function address, or it may still emit two separate but structurally
identical functions. CBaseEntity_GetChangeAccessorPathInfo_2 is already resolved (it inherits its vtable slot
from CEntityInstance_GetChangeAccessorPathInfo_2); CBaseEntity_GetChangeAccessorPathInfo_1 occupies a
different slot within +/-2 entries of it in the same CBaseEntity vtable.
Method
1. Load CBaseEntity_GetChangeAccessorPathInfo_2 from YAML
ALWAYS Use SKILL /get-func-from-yaml with func_name=CBaseEntity_GetChangeAccessorPathInfo_2.
If the skill returns an error, STOP and report to user.
Otherwise, extract:
func_va(the reference implementation address)vfunc_indexvfunc_offsetvtable_name(should beCBaseEntity)
2. Load CBaseEntity VTable from YAML
ALWAYS Use SKILL /get-vtable-from-yaml with class_name=CBaseEntity.
If the skill returns an error, STOP and report to user.
Otherwise, extract:
vtable_numvfuncvtable_entries
3. Enumerate Candidate Slots
Compute the scan window around the known slot:
window_start = max(0, CBaseEntity_GetChangeAccessorPathInfo_2.vfunc_index - 2)window_end = min(vtable_numvfunc - 1, CBaseEntity_GetChangeAccessorPathInfo_2.vfunc_index + 2)
For every index i in [window_start, window_end] except CBaseEntity_GetChangeAccessorPathInfo_2.vfunc_index
itself, read the candidate function address vtable_entries[i].
4. Check for Identical-Address Folding First
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.
- 11d ago First seen · 169 lines · 115 tokens per session scan A 769084c30b4a
find-CBaseEntity_GetChangeAccessorPathInfo_1 is a skill published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 1,725 once invoked, about $0.0006 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.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.