Stats
Actions
Available In
Tags
Help us improve
Share bugs, ideas, or general feedback.
Plugin
ak
Recover cipher algorithms from ARM64 execution traces using the AlgoKiller methodology, with tools for trace analysis, compression, session management, and structured reporting. Includes agents for static analysis offloading and hypothesis auditing.
$
npx claudepluginhub icloudza/algokiller-plugin --plugin akPopularity
Stars
Med: 1·Avg: 272
Installs
Med: 0·Avg: 1
What's Inside
Slash Commands3
Fold
/fold
Run `trace_fold` on the currently-bound trace to produce a block-collapsed derivative trace (typically 99 % compression on hash-loop-heavy traces) and bind to that instead.
Rebind
/rebind
Rebind the currently-bound trace into a fresh `<timestamp>/` session directory while keeping the trace path + mode + output_dir unchanged. Useful when starting a new analysis pass without re-typing the trace path.
Status
/status
Show the current algokiller session state — bound trace, mode, output_dir, ledger summary, artifacts written.
Agents4
binary-static-inspector
/binary-static-inspector
Read-only helper that queries Binary Ninja MCP / BinAssistMCP and static-analysis CLIs (radare2, objdump, strings, otool, class-dump) on behalf of the main agent. Spawn this when a static probe will return >1 KB of disassembly, a function decompile, a symbol cross-reference list, or a full S-box / round-constant table — the subagent does the BN/r2 round trips in its own context and hands back named symbols / structural conclusions, not raw listings. The main session never sees 50 KB of disassembly. Use it for tasks like "find xrefs to sm3_compress", "decompile the function at <addr>", "dump the AES S-box from .rodata", "list strings in the .data segment that match `[a-z]+_key_\\d+`".
hypothesis-reviewer
/hypothesis-reviewer
Independent blue-team reviewer for algokiller Hypothesis Ledger. The main trace-analysis agent MUST spawn this reviewer before any `hypothesis_conclude(final_confidence="high")` call on a load-bearing hypothesis (one that will be cited by the final write_artifact). The reviewer examines the cited hypothesis in isolation — no access to the main agent's reasoning, only the ledger state + raw trace excerpts — and recommends `confirm` / `refute` / `abandon` with reasons. v0.9.1+ — the reviewer records its verdict via `mark_hypothesis_reviewed`, which the server-side conclude(high) gate now requires (FIX
ledger-curator
/ledger-curator
Read-only ledger consistency reviewer. Spawn this near the end of a long ciphertext-recovery / trace-analysis session, BEFORE the main agent calls `write_artifact` on the final `recovered.py` / `report.md`. The curator scans the hypothesis ledger and produces a one-page audit of (a) which concluded hypotheses are cited by name in the planned deliverable, (b) which concluded-but-unreferenced hypotheses should be archived to satisfy the write_artifact bypass-detection gate, (c) any active hypotheses that should be concluded or abandoned before final delivery, (d) any falsification_evidence gaps that would cause `conclude(high)` to fail. This is a sanity pass, not a verdict — the main agent still does the actual conclude/abandon/archive calls.
trace-hexdump-extractor
/trace-hexdump-extractor
Read-only helper for the main trace-analysis / ciphertext-recovery agent. Spawn this when a `trace_hexblock` will return >2 KB of bytes_hex (typical for `NSJSONSerialization dataWithJSONObject:` blocks, large memcpy / sprintf outputs, AES key-buffer dumps). The subagent extracts the hexdump in its own context, parses byte ranges into named fields, and returns a compact structured summary — the main session only ever sees the interpretation, not the raw kilobytes of hex. Use it when a `trace_search` hit shows a hexdump block whose length field exceeds 0x800, or when the main session has already burned context on prior hexdumps and another one is queued.
Skills3
ciphertext
/ciphertext
Strong activation entry for AlgoKiller ciphertext-recovery mode. Bind an ARM64 trace, force-load the ciphertext-recovery methodology, and start cipher / algorithm recovery from a target ciphertext.
general
/general
Strong activation entry for AlgoKiller general trace-analysis mode. Bind an ARM64 trace, force-load the trace-analysis methodology, and answer field semantics / execution flow / detection-point / data-flow questions.
trace-analysis
/trace-analysis
ARM64 trace 通用证据分析方法论。当用户给出一段 ARM64 执行 trace 文件并询问字段含义、执行流、检测点、数据来源、call 边界、buffer 生命周期等开放问题（不属于纯密文还原）时使用。提供搜索键选择、单一目的搜索纪律、call 边界解析、字段语义分层、执行流抽取与检测点分析的完整方法论。激活此 skill 前应已通过 ak MCP 的 bind_trace 工具绑定 trace 文件并选择 mode=general。
MCP Servers1
Stats
Version1.2.0
LanguagePython
Stars45
Forks15
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Critical
Admin access level
Server config contains admin-level keywords
Tags
Help us improve
Share bugs, ideas, or general feedback.
