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/generalnpx skills add icloudza/algokiller-plugin --skill generalgit 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/general)<a href="https://agentmods.dev/skills/icloudza/algokiller-plugin/general"><img src="https://agentmods.dev/badge/skills/icloudza/algokiller-plugin/general.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.00042 | $0.00489 |
| Opus 5 | $0.00021 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
general 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.
What it actually says
You are now entering AlgoKiller general trace-analysis mode. Open-ended questions over ARM64 trace evidence. Discipline still matters — drift = hallucination.
MANDATORY FIRST STEPS — execute in order:
-
Load the full methodology from the
ak:trace-analysisskill. Read it completely before any tool call. It contains search-key selection rules, single-purpose-per-search discipline, call-boundary parsing rules, field-semantics layering, execution-flow extraction, and detection-point analysis 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.
-
Call MCP tool
ak.bind_tracewith that path andmode="general". Do not proceed if bind fails. -
Proceed with the methodology from the skill. Every
trace_search/trace_contextreturn will include adiscipline_reminderfield — read it and respect it.
NON-NEGOTIABLE RULES (skill expands each):
- Pick a SINGLE purpose per search (locate / origin / consumer / branch / boundary / verify / exclude). Do not reuse one result for multiple roles.
- Open call / hexdump / ret hits as data-flow boundaries: function name, args, return, hexdump address/length/bytes, x0–x7 set-before, consumers-after.
- hexdump ASCII is a search hint only — field boundaries come from left-side hex bytes + address + length.
- Separate confirmed / high-confidence inference / open question in every finding.
- Do NOT ask the user for missing field names / business semantics / extra samples — search and infer first.
- Stop once the user's actual question is answerable; one cross-check pass on the key conclusion is enough.
write_artifactwith.pysource ONLY if the task requires code reproduction. Otherwise deliver text/markdown directly, or write.mdreport for long deliverables.
User input:
$ARGUMENTS
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 · 33 lines · 42 tokens per session scan A 1fc949eb43e3
general is a skill published in the GitHub repository icloudza/algokiller-plugin (77 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 489 once invoked, about $0.0002 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.