Fix it
Albasha0x0/Corvus: files to add.
Starting points for the files agents look for, made by fixed templates from public facts. Anything only you know is marked TODO. Read each one, edit it, then add it to your repo yourself. ScBee never changes your repo.
llms.txt
A short description models can read first.
# Corvus > MCP server and CLI for reverse engineering and security analysis of .NET and native binaries (PE, ELF, Mach-O): decompile, search, compare builds, patch. IDA and Ghidra optional. ## Docs - [README](https://github.com/Albasha0x0/Corvus#readme): what it is and how to install it - [Source](https://github.com/Albasha0x0/Corvus): the code - [Licence](https://github.com/Albasha0x0/Corvus/blob/HEAD/LICENSE): Apache-2.0
AGENTS.md
Instructions for coding agents that work inside the repo.
# Corvus MCP server and CLI for reverse engineering and security analysis of .NET and native binaries (PE, ELF, Mach-O): decompile, search, compare builds, patch. IDA and Ghidra optional. ## Build and test - Install: TODO - Test: TODO - Run: TODO ## Conventions - TODO: the rules a new contributor (or agent) must follow ## Do not - TODO: files or actions that are off limits
agent.json
A card other agents can read: what this is and what it can do.
{
"name": "Corvus",
"description": "MCP server and CLI for reverse engineering and security analysis of .NET and native binaries (PE, ELF, Mach-O): decompile, search, compare builds, patch. IDA and Ghidra optional.",
"url": "https://github.com/Albasha0x0/Corvus",
"skills": [
{
"name": "TODO: what it can do",
"description": "TODO: one sentence"
}
]
}
Starting something new? The agent-ready starter is a GitHub template with all of these files, two skills and this check in CI from the first commit.