wiki-arsenal

name

wiki-arsenal

description

Fast PARALLEL wiki lookup engine over wiki/techniques + wiki/payloads + wiki/tools + wiki/cheatsheets for a surface/service/vuln-class. Two modes - quick (one qmd search, cheap, fire constantly) and deep (4 parallel subagents, one per area, merged ready-to-use arsenal card, cached). This is the fast path arsenal that `arsenal` delegates to; the hunt-* skills each inline their own qmd_query and can hand off here for a parallel lookup. Use for "what do I use against <surface>", "arsenal for <X>", "deep/full arsenal", "tool + payload + technique + cheatsheet for <X>", "fast wiki lookup", "parallel wiki search", any "how do I attack/exploit <service|vuln-class>" where you want the documented tooling + payloads before hand-rolling.

wiki-arsenal

The fast, wiki-first lookup engine for "what do I use against this surface". Runs the four knowledge areas in parallel so a deep lookup is one wall-clock, not four serial reads. arsenal delegates here; the hunt-* skills each carry their own wiki-first qmd_query (MCP-independent) and can hand off here for a fast parallel lookup. Never hand-roll from memory when the wiki has the answer.

Input: a surface, service, or vuln-class (e.g. Jenkins on 8080, SSRF, Kerberoasting).

0. Cache check first (0 tokens on a repeat)

Slug the surface (lowercase, non-alnum -> -). If targets/<active-eng>/arsenal/<slug>.md exists, read and return it. Do not re-spend. (<active-eng> = the dir named in targets/active.md.)

Mode: quick (DEFAULT - fire it constantly)

One mcp__wiki-search__qmd_query over the whole index (add a qmd_search keyword pass when the surface is an exact product/CVE string). Group the hits under the four areas and return each as path -> one-line snippet: