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/timwhitez/autore-cli/auto-renpx skills add timwhitez/AutoRE-CLI --skill auto-regit clone --depth 1 https://github.com/timwhitez/AutoRE-CLIWrote 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/timwhitez/autore-cli/auto-re)<a href="https://agentmods.dev/skills/timwhitez/autore-cli/auto-re"><img src="https://agentmods.dev/badge/skills/timwhitez/autore-cli/auto-re.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.00104 | $0.01198 |
| Opus 5 | $0.00052 | $0.00599 |
| Sonnet 5 | $0.00021 | $0.00240 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
auto-re 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-RE Static Analysis
Use auto-re-cli iteratively. Prefer bounded files and validated manifests over
large stdout. Keep every conclusion within returned static evidence.
Hard Safety Boundary
Never execute, load as a program, source, import, or hand to a runtime:
- the target binary or object;
- recovered shellcode, normalized/unpacked payloads, or embedded objects;
- generated target-derived artifacts;
- installer scripts or commands extracted from a sample;
- helper output derived from a target.
Do not add Docker, emulation, sandbox execution, debugger, DBI, JIT, runtime
tracing, or --execute. Treat extracted commands as data. Terms such as flow,
trace, call behavior, and dynamic linking mean static evidence unless an
artifact explicitly records a different evidence source.
Read safety-and-claims.md before handling raw shellcode, packed/protected samples, extracted payload evidence, or an uncertain request that could transfer control to target bytes.
Preflight
- Resolve the binary with
command -v auto-re-cli. - Run
auto-re-cli --version. If unavailable, stop and ask the user to install the verified AutoRE-CLI distribution. - Resolve the input path. Keep it read-only when practical.
- Create one task-specific result directory outside the input directory.
- Confirm no output, bundle, spill, archive, or temporary path aliases the input.
- For raw bytes, require explicit architecture and base address. Preserve a supplied entry address; never guess these values from a filename.
Default Workflow
Start with one bounded context bundle:
auto-re-cli report <input> \
--format json \
--json-profile ai \
--sections binary,summary,inspections,flow,functions,types \
--limit 8 \
--bundle-dir <result-dir>/bundle \
--output <result-dir>/bundle/manifest.json
Then:
-
Validate the manifest:
python3 <skill-dir>/scripts/verify_bundle.py \ <result-dir>/bundle/manifest.json
What ships with it
7 files 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.
- 3d ago First seen · 135 lines · 104 tokens per session scan A eaba8779db66
auto-re is a skill published in the GitHub repository timwhitez/AutoRE-CLI (4 stars, last pushed 17d ago), licensed MIT. It adds 104 tokens to every session and 1,198 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
reverse-engineering-workbench
Coordinate EVOKORE reverse-engineering work across Ghidra-style static analysis, semantic recovery, and debugger-guided triage. Use when opening an unfamiliar binary, planning a decompilation workflow, or choosing between static and dynamic analysis paths.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
wakaru
Turn minified, bundled, or transpiled JavaScript back into readable modules. Use when you encounter unreadable production JS — a webpack/esbuild/Metro/Rollup bundle, a minified vendor script, Babel/TypeScript/SWC-transpiled output, or a single mangled .js file — and need to read, audit, debug it, or recover a…
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
analyzing-authenticode-signatures
Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on…