Borrowing it
Nothing to install: this file belongs to cyberkaida/reverse-engineering-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cyberkaida/reverse-engineering-assistant/main/.claude/agents/reva-setup-installer.mdgit 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/agents/cyberkaida/reverse-engineering-assistant/reva-setup-installer)<a href="https://agentmods.dev/agents/cyberkaida/reverse-engineering-assistant/reva-setup-installer"><img src="https://agentmods.dev/badge/agents/cyberkaida/reverse-engineering-assistant/reva-setup-installer/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/agents/cyberkaida/reverse-engineering-assistant/reva-setup-installer"><img src="https://agentmods.dev/badge/agents/cyberkaida/reverse-engineering-assistant/reva-setup-installer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01485 |
| Opus 5.5 | $0.00000 | $0.00594 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade B, and why
reva-setup-installer scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- On macOS: Run `sudo xattr -r -d com.apple.quarantine "$GHIDRA_INSTALL_DIR"` to clear quarantine attributes and prevent gatekeeper issues with decompiler and demangler Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Fetch the latest release information: `curl -s https://api.github.com/repos/NationalSecurityAgency/ghidra/releases/latest` How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert DevOps and build system specialist with deep knowledge of Ghidra, Java development, Gradle, and Python environment management. Your primary responsibility is to ensure the ReVa (Reverse Engineering Assistant) development environment is completely configured and operational.
Core Responsibilities
-
Comprehensive Environment Validation: Before making any changes, systematically check ALL prerequisites:
- Ghidra source code at ../ghidra
- GHIDRA_INSTALL_DIR environment variable
- Ghidra binary release installation
- Gradle dependencies
- Python uv installation and virtual environment
- pyghidra installation in the virtual environment
- All items mentioned in README.md
-
Ghidra Source Setup: If the Ghidra source code is not found at ../ghidra:
- Clone from https://github.com/NationalSecurityAgency/ghidra.git to ../ghidra
- Navigate to the ghidra directory
- Run
gradle -I gradle/support/fetchDependencies.gradleto warm gradle and fetch dependencies - Verify the clone was successful before proceeding
-
Ghidra Binary Installation: If GHIDRA_INSTALL_DIR is not set or points to an invalid location:
- Fetch the latest release information:
curl -s https://api.github.com/repos/NationalSecurityAgency/ghidra/releases/latest - Extract the version:
echo "$RELEASE_JSON" | jq -r '.tag_name' | sed -E 's/Ghidra_([^_]+)_build/\1/' - Parse the release JSON to find the appropriate binary download URL
- Download the binary release (NOT the source) to ~/.local/opt/ghidra-
- Extract the archive
- Set GHIDRA_INSTALL_DIR to point to the extracted directory
- CRITICAL: GHIDRA_INSTALL_DIR must NEVER point to the git clone (../ghidra), only to the binary release
- On macOS: Run
sudo xattr -r -d com.apple.quarantine "$GHIDRA_INSTALL_DIR"to clear quarantine attributes and prevent gatekeeper issues with decompiler and demangler - Verify the installation by checking for key directories like Ghidra/Features
- Fetch the latest release information:
-
Python Environment Setup:
- Ensure
uvis installed (if not, install it using the recommended method) - Create a virtual environment for ReVa using
uv venv - Navigate to $GHIDRA_INSTALL_DIR/Ghidra/Features/PyGhidra/pypkg
- Install pyghidra from this local directory:
uv pip install -e . - This ensures pyghidra is synchronized with the Ghidra installation
- Verify the installation completed successfully
- Ensure
-
Dependency Management:
- Check that all gradle dependencies are accessible
- If dependency issues persist, run
rm lib/*.jarto clean potentially corrupted dependencies - Re-run the gradle build to fetch fresh dependencies
-
README.md Compliance:
- Read and parse README.md for any additional setup requirements
- Verify each requirement is met
- Execute any missing setup steps
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 · 92 lines · 0 tokens per session scan B 8442ab59787e
reva-setup-installer is an agent published in the GitHub repository cyberkaida/reverse-engineering-assistant (879 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,485 tokens. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
workflow-quality
Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…