What is CS2_VibeSignatures AGENTS.md?

Project instructions for an AI coding agent working in the CS2_VibeSignatures repository. They explain how to use stored project notes, load information only when needed, and record or update notes.

Use them to guide repository onboarding, search and update project notes, and choose targeted tools when notes are missing or outdated.

They help the agent keep context compact while still finding project details, commands, conventions, and completion checks. This reduces unnecessary reading of the entire repository or knowledge base.

How HLND2T/CS2_VibeSignatures configures Codex and OpenCode

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/HLND2T/CS2_VibeSignatures/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/HLND2T/CS2_VibeSignatures

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/hlnd2t/cs2_vibesignatures/agents-md/github.svg)](https://agentmods.dev/instructions/hlnd2t/cs2_vibesignatures/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/hlnd2t/cs2_vibesignatures/agents-md"><img src="https://agentmods.dev/badge/instructions/hlnd2t/cs2_vibesignatures/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/hlnd2t/cs2_vibesignatures/agents-md"><img src="https://agentmods.dev/badge/instructions/hlnd2t/cs2_vibesignatures/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 757 This file is loaded in full into every session.

When invoked 757 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00757	$0.00757
Opus 5.5	$0.00303	$0.00303
Sonnet 5.5	$0.00151	$0.00151
Haiku 4.5	$0.00076	$0.00076

Measured 15d ago against content hash b9606aedd71a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

CS2_VibeSignatures AGENTS.md 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 15d 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.

AGENTS.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file provides guidance for Agent Coding in this repository, using progressive disclosure.

Basic Memory Knowledge Base (Keep Context Compact)

Prefer search_notes to inspect notes available in memory/. Do not read all notes by default.
Use read_note to read a specific note only when needed. Load notes on demand.
If note information is insufficient or outdated, fall back to repository files or targeted lookup through ContextEngine, symbol tools, or search tools. Use write_note, edit_note, or delete_note to maintain notes.

High-Level Repository Information (Prefer Relevant Notes)

The following information was summarized into Basic Memory notes during onboarding and is not repeated here:

Project purpose, technology stack, and key external tools: project_overview
Directory structure, module organization, and data-flow architecture: project_overview
Common development commands: suggested_commands
Code style and conventions: style_and_conventions
Recommended checklist after completing a task: completion_checklist

Additional topic notes (search/read on demand):

Binary acquisition and analysis: download_depot, copy_depot_bin, binary_lock, ida_analyze_bin, warmup_idb
IDA / MCP / decompilation: ida-pro-mcp, idalib-mcp, llm_decompile, ida_vcall_finder, generate_reference_yaml, ida_skill_preprocessor
Signatures and offsets: func_sig, gv_sig, vfunc_sig, offset_sig, symbol_yaml, func_xrefs
Gamedata and release lifecycle: gamedata_metadata, gamesymbol_metadata, gamedata_aliases, config_yaml, update_gamedata, pack_snapshot, post_change_candidate_lifecycle, release-staging
Tests and validation: run_cpp_tests, cpp_tests_util

Source File Entry Points When Memories Are Insufficient (Query and Read on Demand)

Quick overview: README.md / README_CN.md
Dependency information: pyproject.toml, uv.lock
Configuration: .mcp.json, download.yaml, configs/<GAMEVER>.yaml
Main script entry points: download_depot.py, copy_depot_bin.py, ida_analyze_bin.py, generate_reference_yaml.py, gamesymbol_candidate.py, gamedata_candidate.py, run_cpp_tests.py, update_gamedata.py, bin_artifact_contract.py
Large directories. Avoid reading them in full: bin/, bin_artifacts/, s2sdk/, gamedata-generators/, gamesymbol_snapshot_lib/, ida_preprocessor_scripts/, vcall_finder/

Read the full file on GitHub · 47 lines

Changes

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.

15d ago Changed · -2 tokens per session b9606aedd71a
2mo ago First seen · 47 lines · 759 tokens per session scan A 88c927a5a3ac

Subscribe to this mod's changes

CS2_VibeSignatures AGENTS.md is an instructions file published in the GitHub repository HLND2T/CS2_VibeSignatures (67 stars, last pushed today), licensed MIT. It adds 757 tokens to every session, about $0.0030 per session on Opus 5.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-09-06.

Building agents Memory and context

CS2_VibeSignatures AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
CS2_VibeSignatures AGENTS.mdHLND2T/CS2_VibeSignatures	Instructions file	67	today	MIT	A	757	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

CS2_VibeSignatures: Instructions file for Codex