aeondave/solc
offensive-tools/exploits/solc/SKILL.md
solc: Solidity compiler for generating ABI, bytecode, metadata, and standard-json outputs. Use when compiling smart contracts directly, validating compiler settings, producing artifacts for audit tooling, or reproducing builds outside a framework wrapper.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill solcInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 4:36 AM145.5s1 file scanned
SKILL.md
- name:
- solc
- description:
- solc: Solidity compiler for generating ABI, bytecode, metadata, and standard-json outputs. Use when compiling smart contracts directly, validating compiler settings, producing artifacts for audit tooling, or reproducing builds outside a framework wrapper.
- compatibility:
- Linux, Windows, macOS; standalone Solidity compiler
- author:
- AeonDave
- version:
- 1.0
solc
Direct Solidity compilation when you want the compiler, not the framework's interpretation of it.
When to use solc
Use solc when you need to:
- compile a single contract or small set of contracts directly
- produce ABI and bytecode artifacts for deployment or analysis
- confirm optimizer and compiler-version effects explicitly
- feed
slither,mythril, or custom tooling with known compilation inputs
Quick Start
# Emit ABI and bytecode into a build directory
solc --abi --bin Contract.sol -o build
# Enable optimization explicitly
solc --abi --bin --optimize --optimize-runs 200 Contract.sol -o build
High-Value Workflows
Combined output for tooling
solc --combined-json abi,bin,metadata Contract.sol > combined.json
Standard JSON mode
solc --standard-json < input.json > output.json
Practical Notes
- Match the compiler version to the contract's pragma and real deployment assumptions.
- Record optimizer settings; they materially affect bytecode, findings, and source maps.
- Use framework-native compilation for large projects, then fall back to raw
solcwhen you need explicit control.
Caveats
- Import resolution and remappings are easy to get wrong outside a framework.
- Single-file success does not mean a full project will compile cleanly.
- Compiler-version mismatch can invalidate audit conclusions very quickly.
Resources
No bundled scripts/, references/, or assets/.
Use the official Solidity compiler docs for standard JSON schema, optimizer controls, and remapping behavior.
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026