OpenParable
Skip to content
← Back to skills

Strix•Katana 用法

Apps & Automation

Strix•Katana 用法 is an Agent Skill for apps & automation published in the asdfgh1445/ctf-super-hub repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Strix Katana 爬虫命令手册,覆盖深度、JS 抓取与稳定并发控制;触发名:strix-katana

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/asdfgh1445/ctf-super-hub/blob/HEAD/strix-katana/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/strix-katana-用法, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Katana CLI Playbook

Official docs:

Canonical syntax: katana [flags]

High-signal flags:

  • -u, -list <url|file> target URL(s)
  • -d, -depth <n> crawl depth
  • -jc, -js-crawl parse JavaScript-discovered endpoints
  • -jsl, -jsluice deeper JS parsing (memory intensive)
  • -kf, -known-files <all|robotstxt|sitemapxml> known-file crawling mode
  • -proxy <http|socks5 proxy> explicit proxy setting
  • -c, -concurrency <n> concurrent fetchers
  • -p, -parallelism <n> concurrent input targets
  • -rl, -rate-limit <n> request rate limit
  • -timeout <seconds> request timeout
  • -retry <n> retry count
  • -ef, -extension-filter <list> extension exclusions
  • -tlsi, -tls-impersonate experimental JA3/TLS impersonation
  • -hl, -headless enable hybrid headless crawling
  • -sc, -system-chrome use local Chrome for headless mode
  • -ho, -headless-options <csv> extra Chrome options (for example proxy-server)
  • -nos, -no-sandbox run Chrome headless with no-sandbox
  • -noi, -no-incognito disable incognito in headless mode
  • -cdd, -chrome-data-dir <dir> persist browser profile/session
  • -xhr, -xhr-extraction include XHR endpoints in JSONL output
  • -silent, -j, -jsonl, -o <file> output controls

Agent-safe baseline for automation: mkdir -p crawl && katana -u https://target.tld -d 3 -jc -kf robotstxt -c 10 -p 10 -rl 50 -timeout 10 -retry 1 -ef png,jpg,jpeg,gif,svg,css,woff,woff2,ttf,eot,map -silent -j -o crawl/katana.jsonl

Common patterns:

  • Fast crawl baseline: katana -u https://target.tld -d 3 -jc -silent
  • Deeper JS-aware crawl: katana -u https://target.tld -d 5 -jc -jsl -kf all -c 10 -p 10 -rl 50 -o katana_urls.txt
  • Multi-target run with JSONL output: katana -list urls.txt -d 3 -jc -silent -j -o katana.jsonl
  • Headless crawl with local Chrome: katana -u https://target.tld -hl -sc -nos -xhr -j -o crawl/katana_headless.jsonl
  • Headless crawl through proxy: katana -u https://target.tld -hl -sc -ho proxy-server=http://127.0.0.1:48080 -j -o crawl/katana_proxy.jsonl

Critical correctness rules:

  • -kf must be followed by one of all, robotstxt, or sitemapxml.
  • Use documented -hl for headless mode.
  • -proxy expects a single proxy URL string (for example http://127.0.0.1:8080).
  • -ho expects comma-separated Chrome options (example: -ho --disable-gpu,proxy-server=http://127.0.0.1:8080).
  • For -kf, keep depth at least -d 3 so known files are fully covered.
  • If writing to a file, ensure parent directory exists before -o.

Usage rules:

  • Keep -d, -c, -p, and -rl explicit for reproducible runs.
  • Use -ef early to reduce static-file noise before fuzzing.
  • Prefer -proxy over environment proxy variables when proxying only Katana traffic.
  • Use -hc only for one-time diagnostics, not routine crawling loops.
  • Do not use -h/--help for routine runs unless absolutely necessary.

Failure recovery:

  • If crawl runs too long, lower -d and optionally add -ct.
  • If memory spikes, disable -jsl and lower -c/-p.
  • If headless fails with Chrome errors, drop -sc or install system Chrome.
  • If output is noisy, tighten scope and add -ef filters.

If uncertain, query web_search with: site:docs.projectdiscovery.io katana <flag> usage