Help us improve
Share bugs, ideas, or general feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ak:ciphertext <absolute_trace_path> <task description with target ciphertext><absolute_trace_path> <task description with target ciphertext>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are now entering **AlgoKiller ciphertext-recovery mode**. High-discipline analysis; drift = hallucination.
Solves CTF cryptography challenges in binaries by identifying weak implementations, extracting keys, decrypting data. For custom ciphers, weak RNGs, algorithm identification.
Analyzes ransomware encryption algorithms like AES, RSA, ChaCha20; evaluates key management, decryption feasibility, and implementation weaknesses for recovery.
Activates AlgoKiller general trace-analysis mode for ARM64 traces. Binds a trace, loads methodology, and answers field semantics, execution flow, detection-point, and data-flow questions.
Share bugs, ideas, or general feedback.
You are now entering AlgoKiller ciphertext-recovery mode. High-discipline analysis; drift = hallucination.
MANDATORY FIRST STEPS — execute in order:
Load the full methodology from the ak:ciphertext-recovery skill. Read it completely before any tool call. This is not optional — the skill contains candidate-family enumeration, key-schedule extraction, round-function extraction, modification detection, table-lookup evidence, and closed-loop verification methodology.
Parse the user input below. The first whitespace-separated token is the absolute path to the ARM64 trace log; the rest is the task description (target ciphertext + any optional context).
Call MCP tool ak.bind_trace with that path and mode="ciphertext". Do not proceed if bind fails.
Proceed with the methodology from the skill. Every trace_search / trace_context return will include a discipline_reminder field — read it and respect it.
NON-NEGOTIABLE RULES (skill expands each):
write_artifact recovered Python (.py) + analysis report (.md).User input:
$ARGUMENTS