CS2_VibeSignatures: Agent for Claude Code

.claude/agents/sig-finder.md

sig-finder is an agent for Claude Code from HLND2T/CS2_VibeSignatures. It costs 12 tokens per session (212 once invoked), scanned A, original, MIT.

An AI-agent role for reverse engineering programs in IDA, a tool that displays and analyzes compiled code, using IDA MCP tools.

In plain words
What is it for?
It is for finding items in IDA from disassembly, checking the binary platform, and following a defined analysis strategy.
Why use it?
It provides rules for investigating the currently open binary while avoiding brute force and unrelated files.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is HLND2T/CS2_VibeSignatures's own configuration. It tells Claude Code 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 →

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/.claude/agents/sig-finder.md
Clone the repo
git clone --depth 1 https://github.com/HLND2T/CS2_VibeSignatures

Made for: Claude Code.

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 sig-finder

README.md
[![agentmods](https://agentmods.dev/badge/agents/hlnd2t/cs2_vibesignatures/sig-finder/github.svg)](https://agentmods.dev/agents/hlnd2t/cs2_vibesignatures/sig-finder)
Your own site
<a href="https://agentmods.dev/agents/hlnd2t/cs2_vibesignatures/sig-finder"><img src="https://agentmods.dev/badge/agents/hlnd2t/cs2_vibesignatures/sig-finder/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.

agentmods 80×15 button for sig-finder

Your own site · 80×15
<a href="https://agentmods.dev/agents/hlnd2t/cs2_vibesignatures/sig-finder"><img src="https://agentmods.dev/badge/agents/hlnd2t/cs2_vibesignatures/sig-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 212 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00212
Opus 5 $0.00006 $0.00106
Sonnet 5 $0.00002 $0.00042
Haiku 4.5 $0.00001 $0.00021

Measured 9d ago against content hash 8cbb58330bad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sig-finder 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 9d 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.

.claude/agents/sig-finder.md · 15 lines

What it actually says

You are a reverse-engineering expert, your goal is to find stuffs in IDA. You can use the ida-pro-mcp tools to retrieve information. In general use the following strategy:

  • Do not attempt brute forcing, derive any solutions purely from the disassembly and simple python scripts
  • NEVER convert number bases yourself. Use the int_convert MCP tool if needed!
  • ALWAYS use ida-pro-mcp tools to determine the binary platform (.dll or .so) we are analyzing. Do NOT explore bin folder to determine platform.
  • NEVER open or switch to another binary or IDB. Analyze only the file currently opened in IDA, DO NOT call mcp__ida-pro-mcp__open_file.
  • NEVER stop half-way even one of the steps indicates a success, until you finish ALL tasks.
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. 9d ago First seen · 15 lines · 12 tokens per session scan A 8cbb58330bad

Subscribe to this mod's changes

sig-finder is an agent published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 212 once invoked, about $0.0001 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.