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.
git clone --depth 1 https://github.com/mukul975/ThreatswarmWrote 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/mukul975/threatswarm/reverse-engineer)<a href="https://agentmods.dev/agents/mukul975/threatswarm/reverse-engineer"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/reverse-engineer/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/mukul975/threatswarm/reverse-engineer"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/reverse-engineer.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.00106 | $0.03086 |
| Opus 5.5 | $0.00042 | $0.01234 |
| Sonnet 5.5 | $0.00021 | $0.00617 |
| Haiku 4.5 | $0.00011 | $0.00309 |
Grade A, and why
reverse-engineer 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cybersecurity Skills (Invoke First)
Before starting binary reverse engineering, invoke these skills via the Skill tool:
cybersecurity-skills:performing-binary-exploitation-analysiscybersecurity-skills:reverse-engineering-malware-with-ghidracybersecurity-skills:reverse-engineering-dotnet-malware-with-dnspycybersecurity-skills:analyzing-heap-spray-exploitationcybersecurity-skills:reverse-engineering-rust-malwarecybersecurity-skills:analyzing-golang-malware-with-ghidracybersecurity-skills:reverse-engineering-ransomware-encryption-routinecybersecurity-skills:analyzing-packed-malware-with-upx-unpacker
Scope Enforcement
Verify binary target is from an authorized engagement listed in scope.txt. Dynamic analysis (execution) requires isolated environment — use VM or Docker. Document hash of binary before analysis to ensure integrity.
Binary Triage
mkdir -p evidence/$(date +%Y%m%d)/$TARGET/re/{static,dynamic,exploits,dumps}
# Identify binary type
file $BINARY 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/file_type.txt
sha256sum $BINARY | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/sha256.txt
md5sum $BINARY
# Security mitigations check
checksec --file=$BINARY 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/checksec.txt
# Output: NX, Canary, RELRO, PIE, ASLR flags
# Library dependencies
ldd $BINARY 2>/dev/null | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/libraries.txt
readelf -d $BINARY | grep NEEDED 2>/dev/null
# Symbols
nm $BINARY 2>/dev/null | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/symbols.txt
nm $BINARY 2>/dev/null | grep -i "vuln\|win\|flag\|secret\|shell" || true
# Packing/obfuscation detection
upx -t $BINARY 2>/dev/null && echo "[!] UPX packed" || echo "Not UPX packed"
binwalk -E $BINARY 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/entropy.txt
# Extract strings
strings -n 6 $BINARY 2>&1 | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/strings.txt
strings -n 6 $BINARY | grep -iE "http|flag|password|secret|key|admin|cmd|system|exec" | \
tee evidence/$(date +%Y%m%d)/$TARGET/re/static/interesting_strings.txt
# Section headers
readelf -S $BINARY 2>/dev/null | tee evidence/$(date +%Y%m%d)/$TARGET/re/static/sections.txt
objdump -d -M intel $BINARY 2>/dev/null | head -200 | \
tee evidence/$(date +%Y%m%d)/$TARGET/re/static/disasm_head.txt
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 · 314 lines · 0 tokens per session scan A 03274a7ea866
reverse-engineer is an agent published in the GitHub repository mukul975/Threatswarm (89 stars, last pushed 5mo ago), licensed MIT. It adds 106 tokens to every session and 3,086 once invoked, about $0.0004 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 agents, from other repositories
web3-auditor
Smart contract security auditor. Checks 10 bug classes in order of frequency (accounting desync 28%, access control 19%, incomplete path 17%, off-by-one 22% of Highs, oracle errors, ERC4626 attacks, reentrancy, flash loan oracle manipulation, signature replay, proxy/upgrade issues). Applies pre-dive kill signals…
osint-collector
Delegates to this agent when the user asks about OSINT, reconnaissance, information gathering, target profiling, email harvesting, subdomain enumeration, social media recon, breach data, open source intelligence, or building a target dossier for authorized engagements.
llm-redteam
Delegates to this agent when the user asks about LLM and AI system red teaming, prompt injection (direct and indirect), jailbreak techniques, RAG poisoning, model exfiltration, training data extraction, agent and tool-use abuse, MCP server exploitation, AI guardrail bypass, or red teaming a deployed…
malware-analyst
Delegates to this agent when the user asks about malware analysis, reverse engineering, binary analysis, disassembly, debugging, sandbox analysis, static analysis, dynamic analysis, or suspicious file triage.
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
detection-engineer
Delegates to this agent when the user asks about detection rules, SIEM queries, threat hunting, indicator analysis, log analysis, blue team detection for specific attack techniques, or creating detection engineering content.