What is unknown-binary-onboarding?

A first-pass process for examining an unfamiliar binary, library, firmware image, or software package and deciding how to analyze it.

Use it to classify the target, inspect imports, exports, strings, resources, and file sections, choose a suitable analysis tool, and make a priority list of functions or classes.

It creates a focused analysis plan before detailed investigation, so important routines and unanswered questions are identified early.

unknown-binary-onboarding — Skill for Claude Code and Codex by mattmre

Install

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.

Any agent

npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill unknown-binary-onboarding

Clone the repo

git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLIC

Made for: Claude Code, Codex.

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/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding/github.svg)](https://agentmods.dev/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding)

Your own site

<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding/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/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/unknown-binary-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 476 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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.00476
Opus 5	$0.00022	$0.00238
Sonnet 5	$0.00009	$0.00095
Haiku 4.5	$0.00004	$0.00048

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

Security

Grade A, and why

unknown-binary-onboarding 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.

SKILLS/DEVELOPER TOOLS/unknown-binary-onboarding/SKILL.md · 56 lines

What it actually says

Unknown Binary Onboarding

The first session should create an analysis charter, not a mess. This skill keeps the initial pass focused on classification, scoping, and target selection.

Workflow

Record the operator question, constraints, and whether execution is allowed.
Classify the target quickly:
- native PE / ELF / Mach-O
- .NET
- JVM / Android
- firmware / embedded
- suspicious sample needing early capability triage
Run recon before interpretation:
- imports / exports
- strings / resources
- sections / format markers
- compiler or runtime signals
Choose the first specialist lane:
- Ghidra for broad native analysis
- ILSpy for .NET-first work
- JADX or Vineflower for Android / JVM decompilation
- malware triage if suspicious behavior appears early
Produce a target queue of priority routines, subsystems, or artifacts.

Required Outputs

target profile
primary goal
subsystem guesses
first-pass tool choice
priority function or class queue
unresolved questions that drive the next session

Pairings

Use ghidra-core-recon immediately after this skill for native binaries.
Use malware-triage-workflow in parallel if suspicion is non-trivial.
Run orch-panel re in unknown-binary-onboarding mode when the sample is high-risk or strategically important.

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.

9d ago First seen · 56 lines · 44 tokens per session scan A b9e1c913572e

Subscribe to this mod's changes

unknown-binary-onboarding is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 476 once invoked, about $0.0002 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-31.

Debugging agentic-ai aggregator ai-tools claude developer-tools ghidra hitl ilspy jadx onboarding reverse-engineering triage

reverse-engineering-android-malware-with-jadx

Reverse engineers malicious Android APK files using JADX decompiler to analyze Java/Kotlin source code, identify malicious functionality including data theft, C2 communication, privilege escalation, and overlay attacks. Examines manifest permissions, receivers, services, and native libraries. Activates for requests…

adriannoes/awesome-agentic-ai · 82 tokens

ts-debug

TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".

berekvolgyipeter/dotclaude · 68 tokens

py-debug

Python debugging expert. Use when the user needs to debug, profile, or trace Python code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function".

berekvolgyipeter/dotclaude · 54 tokens

deep-analysis

Performs focused, depth-first investigation of specific reverse engineering questions through iterative analysis and database improvement. Answers questions like "What does this function do?", "Does this use crypto?", "What's the C2 address?", "Fix types in this function". Makes incremental improvements (renaming…

cyberkaida/reverse-engineering-assistant · 98 tokens

ctf-rev

Solve CTF reverse engineering challenges using systematic analysis to find flags, keys, or passwords. Use for crackmes, binary bombs, key validators, obfuscated code, algorithm recovery, or any challenge requiring program comprehension to extract hidden information.

cyberkaida/reverse-engineering-assistant · 52 tokens

pyghidra-scripting

Write and run Python (PyGhidra) code inside the Ghidra session that ReVa's MCP server is already attached to, using the five ReVa scripting tools — run-script, list-scripts, read-script, write-script, edit-script. Use this whenever the user asks to execute Python against the current program, reach for the Ghidra Flat…

cyberkaida/reverse-engineering-assistant · 209 tokens