Menu
Katana crawler syntax, depth/js/known-files behavior, and stable concurrency controls.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | katana-tooling |
| description | Katana crawler syntax, depth/js/known-files behavior, and stable concurrency controls. |
penkit51 AI — professional penetration testing skill pack. Authorized testing only.
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 controlsAgent-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:
katana -u https://target.tld -d 3 -jc -silentkatana -u https://target.tld -d 5 -jc -jsl -kf all -c 10 -p 10 -rl 50 -o katana_urls.txtkatana -list urls.txt -d 3 -jc -silent -j -o katana.jsonlkatana -u https://target.tld -hl -sc -nos -xhr -j -o crawl/katana_headless.jsonlkatana -u https://target.tld -hl -sc -ho proxy-server=http://127.0.0.1:48080 -j -o crawl/katana_proxy.jsonlCritical correctness rules:
-kf must be followed by one of all, robotstxt, or sitemapxml.-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).-kf, keep depth at least -d 3 so known files are fully covered.-o.Usage rules:
-d, -c, -p, and -rl explicit for reproducible runs.-ef early to reduce static-file noise before fuzzing.-proxy over environment proxy variables when proxying only Katana traffic.-hc only for one-time diagnostics, not routine crawling loops.-h/--help for routine runs unless absolutely necessary.Failure recovery:
-d and optionally add -ct.-jsl and lower -c/-p.-sc or install system Chrome.-ef filters.If uncertain, query web_search with:
site:docs.projectdiscovery.io katana <flag> usage
Complementary crawlers / JS endpoint extractors in the sandbox:
gospider -s https://target.tld -d 3 -c 10 -t 20 — alternate crawler;
picks up things Katana misses on weird sites; use it as a second
pass when Katana output looks thin.~/tools/JS-Snooper/js_snooper.sh <domain> and
~/tools/jsniper.sh/jsniper.sh <domain> — both take a bare domain and
run their own JS-file discovery internally (jsniper drives httpx +
katana + nuclei file templates). Reach for them when you want a quick
"find endpoints/keys/secrets in any JS this domain serves" sweep
without wiring it up yourself.penkit51 AI — professional penetration testing skill pack. Authorized testing only.
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 controlsAgent-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:
katana -u https://target.tld -d 3 -jc -silentkatana -u https://target.tld -d 5 -jc -jsl -kf all -c 10 -p 10 -rl 50 -o katana_urls.txtkatana -list urls.txt -d 3 -jc -silent -j -o katana.jsonlkatana -u https://target.tld -hl -sc -nos -xhr -j -o crawl/katana_headless.jsonlkatana -u https://target.tld -hl -sc -ho proxy-server=http://127.0.0.1:48080 -j -o crawl/katana_proxy.jsonlCritical correctness rules:
-kf must be followed by one of all, robotstxt, or sitemapxml.-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).-kf, keep depth at least -d 3 so known files are fully covered.-o.Usage rules:
-d, -c, -p, and -rl explicit for reproducible runs.-ef early to reduce static-file noise before fuzzing.-proxy over environment proxy variables when proxying only Katana traffic.-hc only for one-time diagnostics, not routine crawling loops.-h/--help for routine runs unless absolutely necessary.Failure recovery:
-d and optionally add -ct.-jsl and lower -c/-p.-sc or install system Chrome.-ef filters.If uncertain, query web_search with:
site:docs.projectdiscovery.io katana <flag> usage
Complementary crawlers / JS endpoint extractors in the sandbox:
gospider -s https://target.tld -d 3 -c 10 -t 20 — alternate crawler;
picks up things Katana misses on weird sites; use it as a second
pass when Katana output looks thin.~/tools/JS-Snooper/js_snooper.sh <domain> and
~/tools/jsniper.sh/jsniper.sh <domain> — both take a bare domain and
run their own JS-file discovery internally (jsniper drives httpx +
katana + nuclei file templates). Reach for them when you want a quick
"find endpoints/keys/secrets in any JS this domain serves" sweep
without wiring it up yourself.record_vulnerability when running inside the penkit51 platformrecord_vulnerability when running inside the penkit51 platformAuthorized AI penetration testing assistant for web applications, APIs, and infrastructure. Performs reconnaissance, vulnerability assessment, PoC validation, exploit chaining, and professional reporting. Use when the user asks for pentest, penetration test, security assessment, vulnerability scan, bug bounty research, authorized hacking, SQLi/XSS/IDOR/SSRF testing, API security audit, or exploit validation.
Authorized AI penetration testing for web apps, APIs, cloud, and infrastructure. Full kill-chain methodology with PoC validation, vulnerability chaining, and professional reporting. Triggers on: pentest, penetration test, security assessment, vuln scan, bug bounty, red team, authorized hack, SQL injection test, XSS test, IDOR, SSRF, API security, exploit validation, security audit.
Authorized AI penetration testing assistant — full-spectrum security testing with deep exploitation skills and integrated tooling. Use for web app pentests, API security, vuln validation, PoC development, bug bounty, and security assessments. Triggers on pentest, penetration test, security audit, exploit, SQLi, XSS, IDOR, SSRF.
API安全测试的专业技能和方法论
JWT and OIDC security testing covering token forgery, algorithm confusion, and claim manipulation
AWS cloud security testing covering IAM misconfigurations, S3 exposure, metadata abuse, and privilege escalation paths