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 agentmods add skills/xamirhamza77/reverseops-skill/go-rust-reversenpx skills add xAmirHamza77/ReverseOps-Skill --skill go-rust-reversegit clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-SkillWrote 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/xamirhamza77/reverseops-skill/go-rust-reverse)<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/go-rust-reverse"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/go-rust-reverse.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00514 |
| Opus 5 | $0.00019 | $0.00257 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
go-rust-reverse 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 yesterday.
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.
What it actually says
Go / Rust Binary Reverse Engineering
ACTION REQUIRED (execute immediately after reading)
NOW: Read../field-journal/precedent-reverse.mdNOW: Confirm the sample is a Go/Rust build artifact (file/ strings / runtime characteristics)NEXT: Check whether GoReSym / related plugins are availableACT: Runtime identification → symbol/metadata recovery → business logic
Applicable scenarios
- Stripped Go malware/tools
- Rust release binaries, panic-string-driven analysis
- Language-specific methods complementary to general IDA/Ghidra workflows
Workflow
Go
□ Identify go.buildid, leftover runtime symbols, pclntab
□ Restore function names with GoReSym / redress / IDA Go plugins
□ Pay attention to how interface, slice, and string structures appear in decompilation
□ Networking/crypto library paths: crypto/* net/http
Rust
□ Panic strings, rust_begin_unwind, crate path hints
□ Code bloat caused by generic instantiation; locate string xrefs first
□ Async/tokio state machines need to be understood together with cross-references
Dynamic
□ Frida is still usable; watch out for Go stacks and scheduling
□ Prefer log- and config-string-driven breakpoints
Toolchain
| Tool | Purpose |
|---|---|
| GoReSym | Go metadata |
| IDA/Ghidra + Go/Rust plugins | Decompilation |
| radare2 | Quick strings |
| strings / rabin2 | Triage |
References
references/go-rust-notes.md../reverse-engineering/go-reverse.md../ida-reverse/../ghidra-reverse/- seed:
field-journal/seed-002_go-malware-stripped.md
Routing context
Upstream: MASTER R33
Downstream: Malicious sample workflow malware-analysis; general RE reverse-engineering
Task completion self-check
- Did I restore key function names or an equivalent mapping?
- Did I annotate the language runtime evidence?
- Checklist?
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 72 lines · 38 tokens per session scan A 3de225effe36
go-rust-reverse is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 514 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-09-03.
Other skills, from other repositories
test
Skill "test" from usk6666/yorishiro-proxy, covering /test, default behavior, argument patterns and steps.
port-from-go
Port Go into Rust — goroutines and channels onto tasks and async, interfaces onto traits, error values onto Result, and the value-semantics traps (zero values, integer wraparound, slice aliasing, nil). Use when porting, rewriting, or migrating Go, Golang, a Go service, or a Go CLI into Rust, when replacing a Go…
polars
High-performance DataFrame library for Python ETL, analytics, and pandas migration. Use for expression-based data manipulation with lazy query optimization, parallel execution, streaming out-of-core processing, Arrow interoperability, and optional GPU execution.
go-rust-reverse
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.
update-keyboard-shortcuts
Audits and synchronizes keyboard shortcuts across docs/keyboardshortcuts.md, crates/regenerator2000-tui/src/ui/dialogkeyboardshortcut.rs, crates/regenerator2000-tui/src/ui/menu.rs, and the view files (viewdisassembly.rs, viewhexdump.rs, viewcharset.rs, viewbitmap.rs, viewblocks.rs, viewsprites.rs).
eplan-development
Develop EPLAN Electric P8 scripts, API extensions, and remote-control applications. Use when writing C# scripts for EPLAN (actions, event handlers, ribbon), accessing the EPLAN API (parts database, projects, pages), building external apps that drive EPLAN via Remote Client, or debugging EPLAN automation issues…