agentmods.dev

CS2_VibeSignatures: Instructions file for Codex

AGENTS.md

CS2_VibeSignatures AGENTS.md is an instructions file for Codex, OpenCode from HLND2T/CS2_VibeSignatures. It costs 759 tokens per session, scanned A, original, MIT.

AGENTS.md instructions for HLND2T/CS2_VibeSignatures, covering agents.md, basic memory knowledge base (keep context compact), high-level repository information (prefer relevant notes), progressive disclosure guidelines and explore skills.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions AGENTS.md; mentions Codex.

This is HLND2T/CS2_VibeSignatures's own configuration. It tells Codex and OpenCode how to work on CS2_VibeSignatures itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything CS2_VibeSignatures configures →

not rated 65repo today A scan 759 tokens MIT
View source ↗ HLND2T/CS2_VibeSignatures
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.

agentmods badge for CS2_VibeSignatures AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hlnd2t/cs2_vibesignatures/agents-md.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 759 This file is loaded in full into every session.
When invoked 759 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 unknown 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00759 $0.00759
Opus 5 $0.00380 $0.00380
Sonnet 5 $0.00152 $0.00152
Haiku 4.5 $0.00076 $0.00076

Measured today against content hash 88c927a5a3ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 today.

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)

  1. Prefer search_notes to inspect notes available in memory/. Do not read all notes by default.
  2. Use read_note to read a specific note only when needed. Load notes on demand.
  3. 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/, hl2sdk_cs2/, 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.

  1. today 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 (65 stars, last pushed today), licensed MIT. It adds 759 tokens to every session, about $0.0038 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-09-06.

Memory and contextProductivity
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens