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 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/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/skills/timwhitez/autore-cli/auto-re"><img src="https://agentmods.dev/badge/skills/timwhitez/autore-cli/auto-re.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.00082 | $0.01793 |
| Opus 5.5 | $0.00033 | $0.00717 |
| Sonnet 5.5 | $0.00016 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00179 |
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-RE Static Analysis
When a relevant input is available, collect static evidence before answering. Do not substitute a plan, generic reverse-engineering advice, or guessed behavior for a tool call. Do not require the user to name Auto-RE. Respect explicit no-tool requests, unavailable tooling, and the host's permission policy. Conceptual questions and source-code-only reviews do not require this Skill.
Run the trusted analyzer, never the analyzed program. Prefer bounded files; 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/object, recovered shellcode, unpacked/embedded payloads, extracted
scripts/commands, or any other target-derived artifact (including helper output).
Do not add Docker, emulation, sandbox execution, debugger, DBI, JIT, runtime
tracing, or --execute. Extracted commands are data. Flow, trace, call behavior,
and dynamic linking mean static evidence, not observed runtime behavior.
Read safety-and-claims.md before raw shellcode, packed/protected samples, extracted payloads, or uncertain execution boundaries.
First Evidence: One Call
For open-ended questions, invoke the launcher with the supplied input and a
new result directory. Its parent must exist; keep it outside the input
file's resolved parent directory and all its descendants, and outside the Skill,
so analysis output stays separate from samples. For example, use samples/input
and a separate results/run-1, not samples/results:
python3 <skill-dir>/scripts/start_analysis.py <input> --result-dir <new-result-dir>
On Windows use py -3 instead of python3; consult
platform-invocation.md only as needed.
The helper checks paths and Skill readiness, invokes one bounded AI-JSON report,
and returns result_path and receipt_path. Read result_path, including
warnings, budget, completion and next_actions. The summary alone is not
analysis evidence; wrapper success or exit 0 does not prove completeness.
What ships with it
16 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.
- agents/openai.yaml 615 B
- evals/trigger_cases.json 5.5 KB
- references/command-routing.md 9.7 KB
- references/compact-ai-view.md 3.1 KB
- references/evidence-contract.md 24 KB
- references/investigation-workflows.md 15 KB
- references/platform-invocation.md 1.5 KB
- references/safety-and-claims.md 3.1 KB
- scripts/compact_result.py 6.2 KB runs code
- scripts/process_control.py 18 KB runs code
- scripts/read_result.py 14 KB runs code
- scripts/run_next_action.py 73 KB runs code
- scripts/skill_doctor.py 13 KB runs code
- scripts/start_analysis.py 11 KB runs code
- scripts/verify_bundle.py 29 KB runs code
- VERSION 7 B
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 Changed · -63 lines 33148d0f856e
- 13d ago Changed · +8 lines 9ae13183a8c8
- 14d ago Changed · +4 lines 35f26c02673a
- 27d ago Changed · +4 lines 547057669cff
- 1mo ago Changed · +2 lines a3bd5a0c457d
- 1mo ago Changed · +10 lines 691078c3f6d1
- 1mo ago Changed · +26 lines cb5c6f313fd6
- 1mo ago Changed · +23 lines · -22 tokens per session 395247d2e40e
- 1mo 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 (6 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 1,793 once invoked, about $0.0003 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-31.
Other skills, from other repositories
analyzing-rust-malware-internals
Analyzes Rust-compiled malware by detecting the Rust toolchain signature, demangling Rust v0/legacy symbol names, and identifying crate dependencies from embedded paths. Activates for requests to analyze Rust malware, demangle Rust symbols, or identify a Rust binary build and its crates.
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.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.