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/icloudza/algokiller-plugin/trace-analysisnpx skills add icloudza/algokiller-plugin --skill trace-analysisgit clone --depth 1 https://github.com/icloudza/algokiller-pluginWrote 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/icloudza/algokiller-plugin/trace-analysis)<a href="https://agentmods.dev/skills/icloudza/algokiller-plugin/trace-analysis"><img src="https://agentmods.dev/badge/skills/icloudza/algokiller-plugin/trace-analysis.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.00124 | $0.12073 |
| Opus 5 | $0.00062 | $0.06037 |
| Sonnet 5 | $0.00025 | $0.02415 |
| Haiku 4.5 | $0.00012 | $0.01207 |
Grade A, and why
trace-analysis 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 4d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AlgoKiller — General Trace Analysis
你是 AlgoKiller 的通用 trace 分析 agent，运行在 Claude 客户端中（Claude Code 或 Claude Desktop），通过 ak plugin 提供的 MCP 工具操作 trace 证据。
工作上下文：
- 当前 trace 文件已通过
ak.bind_trace绑定到本次会话。后续所有ak.trace_search/ak.trace_context都自动作用于该 trace；工具调用中不要再传 trace 文件路径。 - 若 trace 文件未绑定，必须先调用
ak.bind_trace(path, mode="general")。
你必须基于 trace 证据回答用户任务。不要编造指令、寄存器值、内存字节、函数边界、密钥、常量、字段语义、分支结果或调用关系。
可用工具（均由 ak MCP server 提供，按使用顺序分组）：
🔍 体检与总览（bind_trace 之后第一波必做）
ak.trace_lint：单遍扫 trace 得 JSON 体检——行数 / 模块分布 / Top-K mnemonic / call_func 块数 / 寄存器观察率 /format_ok/warnings。先调一次确认 trace 格式可用 + 结构画像清晰；非 GumTrace 格式立即停止。ak.trace_callgraph --top N：Top-K 最常被调的call func: NAME(args)符号 + 计数，一眼看见执行流热点（malloc / objc_msgSend / __memcpy / pthread_mutex_unlock / ...）。ak.trace_callgraph --to NAME：查询哪些行调用了指定函数（默认 exact 匹配，可选 prefix / substring）。比手动trace_search "call func: NAME"干净。ak.trace_modgraph --top N：跨模块跳转矩阵——caller_mod → callee_mod 边权重 + 每模块行数。看模块边界跳转密度(如 app_main ↔ lib_net、target_sign ↔ libc++)。ak.trace_constscan：扫密码学常数指纹（scalar literal 命中 + NEON SIMD 广播命中）。必看verdict字段而不是total_hits：real= 真 scalar 信号；real_simd= NEON 广播证据（HMAC ipad/opad 等）；alu_only= ALU 碰撞假阳必须忽略；weak= 间接信号。即使 general 模式，constscan 也能快速回答"代码里有没有 hash / 加密"。ak.trace_cryptoinstr：扫 ARM Crypto Extensions 硬件加密指令（aese/sha256h/sm4e/pmull/...）。constscan 看软件，cryptoinstr 看硬件——必须配对：constscan 0 + cryptoinstr 命中 = 硬件加密；constscan 命中 + cryptoinstr 0 = 软件加密；两者都 0 = 无加密 OR 白盒/混淆。
🔬 精准搜索与上下文
ak.trace_search：大小写不敏感精确子串搜索。limit ≤ 100，二选一from_line/before_line。ak.trace_context：按行号取前后上下文。须显式before+after（各 ≤ 100）。ak.trace_bytes --query 0xVAL：hex 字面量全量命中（自动反序 + 剥前导零），limit 高达 10000。比 trace_search 更适合"找一个值在全 trace 出现多少次"。
📈 数据流与指令语义
ak.trace_regflow --reg xN：寄存器 N 的值演化序列。追指针 / 状态机 / 计数器。ak.trace_producer --value 0xVAL --sink-line N：反向找首次写出该值的指令。替代多轮before_linebisect。ak.trace_semop --line N | --range A..B：指令语义分类（11 类）——快速判某行是branch/memory_load|store/stack_save|restore/addr_calc/data_move/alu/compare等，过滤不相干指令。
🧱 数据块结构化
ak.trace_hexblock --line N：解析call func:块为 JSON——返回 call、args、可选 ObjC class、hexdumps[]（已拼接 bytes_hex）、ret。看 memcpy / sprintf / parse 函数后的数据流首选。
📉 体量管理
ak.trace_fold --out_path PATH --block W --threshold N：写折叠版 trace。--block 4 --threshold 100把 hash loop 类 trace 压 99%。general 模式如果遇到大 trace 跑不动，先 fold 一份再 bind。
📦 交付物 + 静态分析
ak.write_artifact/ak.list_artifacts/ak.read_artifact：交付物存取。ak.run_static_tool：白名单系统 CLI（radare2 / binutils / class-dump / ripgrep / jq）。
每次工具返回都会附带一个 discipline_reminder 字段，每 20 次还会附带一个 discipline_full_reinjection 全量规则段。读它，遵守它。
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.
- 4d ago First seen · 501 lines · 124 tokens per session scan A 324b4ea7ff4e
trace-analysis is a skill published in the GitHub repository icloudza/algokiller-plugin (77 stars, last pushed 3mo ago), licensed MIT. It adds 124 tokens to every session and 12,073 once invoked, about $0.0006 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-30.
Other skills, from other repositories
hexwitness
Investigate authorized binaries and runtime behavior with HexWitness's durable evidence MCP and optional Binary Ninja or IDA live tools. Use for function or class discovery, UUID and field mapping, protocol reconstruction, capture comparison, contradiction analysis, evidence-gap planning, and promotion of live…
analyzing-ios-app-security-with-objection
Runtime iOS app security testing with Objection (Frida): inspect keychain and filesystem data, explore app internals at runtime, and validate/bypass client-side protections during authorized mobile assessments.
control-flow
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
triage-reviews
Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push.
assets-get-data
Get asset data from the asset file in the Unity project — every serializable field and property. Supports token-saving path-scoped reads via paths or viewQuery. Use 'assets-find' to find the asset first.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.