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 skills add cyberkaida/reverse-engineering-assistant --skill binary-triagegit clone --depth 1 https://github.com/cyberkaida/reverse-engineering-assistantWrote 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/cyberkaida/reverse-engineering-assistant/binary-triage)<a href="https://agentmods.dev/skills/cyberkaida/reverse-engineering-assistant/binary-triage"><img src="https://agentmods.dev/badge/skills/cyberkaida/reverse-engineering-assistant/binary-triage/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/cyberkaida/reverse-engineering-assistant/binary-triage"><img src="https://agentmods.dev/badge/skills/cyberkaida/reverse-engineering-assistant/binary-triage.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.00065 | $0.01759 |
| Opus 5.5 | $0.00026 | $0.00704 |
| Sonnet 5.5 | $0.00013 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
binary-triage 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 1mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binary Triage
Instructions
We are triaging a binary to quickly understand what it does. This is an initial survey, not deep analysis. Our goal is to:
- Identify key components and behaviors
- Flag suspicious or interesting areas
- Create a task list of next steps for deeper investigation
Binary triage with ReVa
Follow this systematic workflow using ReVa's MCP tools:
1. Identify the Program
- Use
get-current-programto see the active program - Or use
list-project-filesto see available programs in the project - Note the
programPath(e.g., "/Hatchery.exe") for use in subsequent tools
2. Survey Memory Layout
- Use
get-memory-blocksto understand the binary structure - Examine key sections:
.text- executable code.data- initialized data.rodata- read-only data (strings, constants).bss- uninitialized data
- Flag unusual characteristics:
- Unusually large sections
- Packed/encrypted sections
- Executable data sections
- Writable code sections
3. Survey Strings
- Use
get-strings-countto see total string count - Use
get-stringswith pagination (100-200 strings at a time) - Look for indicators of functionality or malicious behavior:
- Network: URLs, IP addresses, domain names, API endpoints
- File System: File paths, registry keys, configuration files
- APIs: Function names, library references
- Messages: Error messages, debug strings, log messages
- Suspicious Keywords: admin, password, credential, token, crypto, encrypt, decrypt, download, execute, inject, shellcode, payload
4. Survey Symbols and Imports
- Use
get-symbols-countwithincludeExternal=trueto count imports - Use
get-symbolswithincludeExternal=trueandfilterDefaultNames=true - Focus on external symbols (imports from libraries)
- Flag interesting/suspicious imports by category:
- Network APIs: connect, send, recv, WSAStartup, getaddrinfo, curl_*, socket
- File I/O: CreateFile, WriteFile, ReadFile, fopen, fwrite, fread
- Process Manipulation: CreateProcess, exec, fork, system, WinExec, ShellExecute
- Memory Operations: VirtualAlloc, VirtualProtect, mmap, mprotect
- Crypto: CryptEncrypt, CryptDecrypt, EVP_, AES_, bcrypt, RC4
- Anti-Analysis: IsDebuggerPresent, CheckRemoteDebuggerPresent, ptrace
- Registry: RegOpenKey, RegSetValue, RegQueryValue
- Note the ratio of imports to total symbols (heavy import usage may indicate reliance on libraries)
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.
- 1mo ago First seen · 156 lines · 65 tokens per session scan A 1a79f775c1d1
binary-triage is a skill published in the GitHub repository cyberkaida/reverse-engineering-assistant (879 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 1,759 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
osgrep-reference
Comprehensive CLI reference and search strategies for osgrep semantic code search. Use for detailed CLI options, index management commands, search strategy guidance (architectural vs targeted queries), and troubleshooting. Complements the osgrep plugin which handles daemon lifecycle.
broadside
Interpret a Broad-Side batch reconnaissance run. Use after codecartobroadside collect has produced .codecarto/broadside/ / results, to triage scouting signals before or during an interactive CodeCartographer pipeline run.
scan-for-defects
Run a multi-pass defect scan across the source codebase, checking for logic errors, error handling gaps, concurrency bugs, security issues, API contract violations, and configuration hazards. Use after the architecture phase is complete. Optionally leverages contracts and protocols outputs for spec-grounded analysis.
scan-for-defects-semantic
Run the deep, semantic subset of the multi-pass defect scan — bugs that need contracts and protocols context to spot. Run after protocols, before porting. Covers concurrency and resource management, security and trust boundaries, and API contract violations (including state machine drift). The mechanical subset…
scan-for-defects-mechanical
Run the early, mechanical subset of the multi-pass defect scan — local bugs that do not need contracts or protocols context to spot. Run after the architecture phase, before contracts. Covers logic and correctness, error handling and resilience, and configuration and environment hazards. The semantic subset…
reverse-engineering-workbench
Coordinate EVOKORE reverse-engineering work across Ghidra-style static analysis, semantic recovery, and debugger-guided triage. Use when opening an unfamiliar binary, planning a decompilation workflow, or choosing between static and dynamic analysis paths.