Global Settings (User-Scoped)

Global Settings is the personal configuration page for the current user. Settings configured here apply across all projects. It is accessible from the gear icon in the top navigation bar (far right).

The page is divided into seven sections: LLM Providers, Agent Skills, Chat Skills, Tradecraft, API Keys & Tunneling, MCP Tool Plugins, and System.

LLM Providers

Configure the AI model providers that power the agent. All providers added here become available in the model selector of every project's settings.

Each provider card shows its icon, name, type, and — for OpenAI-Compatible entries — the model identifier. You can edit, delete, or test each provider from its card.

Click Add Provider to register a new provider. Choose the type (OpenAI, Anthropic, Google Gemini, DeepSeek, GLM, Kimi, Qwen, xAI, Mistral, OpenRouter, AWS Bedrock, or OpenAI-Compatible), enter your credentials, and test the connection before saving. Each form includes a "Get API key →" link to the provider's official console.

For full details on supported providers, model discovery, and setup guides, see AI Model Providers.

API Keys

Store API keys for external OSINT and reconnaissance services. These keys are saved per-user in the database and are used by both the AI agent's tools and the recon pipeline at runtime.

Secret Multiscanner

The Secret Multiscanner has its own key group, one key per source, rendered under the heading Secret Multiscanner on this page. They are deliberately separate from the github.com tokens above. A source whose key is mandatory cannot start until it is set, and the scan card names the missing one. Keys are stored per user and are never included in a project export.

These keys can also be set inline from each source card in project settings, without leaving the form.

Uncover (Multi-Engine Search)

These keys are used exclusively by the Uncover target expansion module (GROUP 2b). They are optional -- uncover also reuses any Shodan, Censys, FOFA, ZoomEye, Netlas, or CriminalIP key configured above.

Each field is a secret input with an eye icon to toggle visibility. Signup links are provided next to each field to help you obtain a key. After entering or updating a key, click Save Settings to persist the change.

Note: All API keys are stored exclusively in the database via this page (user-scoped). They are not read from environment variables or project settings.

Key Rotation

Each API key field has a Key Rotation button on the right side. This lets you configure multiple keys per tool for automatic round-robin rotation to avoid rate limits.

Click the button to open the rotation modal:

1. Extra API Keys — paste additional keys, one per line. These keys plus the main key form the rotation pool. All keys are treated equally.
2. Rotate Every N Calls — after this many API calls, the system switches to the next key in the pool (default: 10).

Once configured, a badge below the field shows the total key count and rotation interval (e.g., "3 keys total, rotate every 10 calls").

Tip: Key rotation is especially useful for NVD (rate-limited to 5 requests/30s without a key), Shodan (paid plans have per-key quotas), the 7 OSINT threat intelligence tools (Censys, FOFA, OTX, Netlas, VirusTotal, ZoomEye, CriminalIP), and the Uncover-specific engines (Quake, Hunter, PublicWWW, HunterHow, Onyphe, Driftnet). With multiple keys, you can multiply your effective rate limit and avoid scan interruptions from per-key quotas.

Agent Skills

Upload and manage custom attack workflow skills (.md files) that teach the agent exploitation techniques beyond the built-in CVE, brute-force, and phishing workflows.

Each skill card shows the skill name, description, and upload date, with actions to edit description, download, or delete.

• Upload Skill (.md) — select a Markdown file, enter a descriptive name and an optional short description (1-2 sentences used by the Intent Router for classification), then click Upload.
• Edit description — click the pencil icon on any skill to update its description without re-uploading the file.
• Delete — removes the skill and automatically disables it in all project configurations.

Uploaded skills appear as toggles in every project's settings, so each project can independently choose which skills to enable.

For details on writing skill files, classification, and built-in skills, see Agent Skills.

Chat Skills

Upload and manage on-demand reference skills for the AI agent chat. Unlike Agent Skills above (which drive attack classification and phase-aware workflows), Chat Skills are tactical reference docs -- tool playbooks, vulnerability guides, framework notes -- that you inject into the agent's context on the fly using /skill <name> in the chat.

Each skill card shows the skill name, description, category badge, and upload date, with actions to edit description, download, or delete.

• Import from Community -- bulk-imports all reference skills from the community folder (agentic/skills/) into your library. The folder starts empty; click this to populate it with the 46 shipped skills (vulnerabilities, tooling, protocols, technologies, frameworks, Active Directory, cloud, post-exploitation). Skills with the same name are skipped.
• Upload Skill (.md) -- upload a custom reference document with name, description, and category.
• Delete -- removes the skill from your library.

Skills uploaded here become available via /skill <name> in all your chat sessions.

For full details on the /skill command, writing Chat Skill files, and the complete comparison with Agent Skills, see Chat Skills.

Tradecraft

Curate a personal catalog of trusted security knowledge URLs (HackTricks, PayloadsAllTheThings, CVE PoC repos, vendor research blogs, ...). Each enabled resource becomes a slug the agent can target through the tradecraft_lookup tool during the exploitation and post-exploitation phases.

Unlike web_search (which queries the open web through Tavily) or the FAISS Knowledge Base (which is pre-ingested at install time), Tradecraft is always live and always curated by you. The agent only sees what you explicitly trusted.

For the full lifecycle, type catalog, cache layer, and agent-session flow, see the dedicated Tradecraft Lookup page.

Resources screen

The screen is laid out as:

Per-card fields

Per-card actions

Verify is asynchronous. Adding a resource creates the row immediately so the card appears with a verifying… chip; the actual fetch + sitemap build + summary runs in the background. The settings page polls every 5 seconds while any resource is unverified, so the badge auto-updates when verify completes.

Add Tradecraft Resource modal

The modal has two halves: the Quick Add catalog at the top and the resource form below.

Quick Add (51 curated resources)

A scrollable list of hand-picked, well-maintained, openly-licensed reference sites, spread across all six resource types so users can populate the catalog with one click. Selecting a row fills Name and URL from the preset; you can still tweak them before saving. The chip on the right is just a hint — the backend always re-detects the type at verify time.

The presets are grouped by type below. Use this list to understand which resource type each well-known site falls into:

mkdocs-wiki

gitbook

github-repo

cve-poc-db

sphinx-docs

agentic-crawl

Form fields

Why no "type" field? Resource type is always auto-detected at verify time from the homepage HTML. A manual override would let users misclassify a site (e.g. mark a generic blog as mkdocs-wiki), which then breaks the sitemap builder. The chip on each Quick Add row is a hint, not a setting.

Resource type differences

The six resource types are not interchangeable — each one drives a different sitemap-extraction strategy, a different cache TTL, and a different at-query-time fetch path. Pick the right type or, equivalently, pick a URL whose homepage will trigger the right detector.

What each type means in practice

• mkdocs-wiki — for MkDocs / Material / mdBook wikis. They publish a complete sitemap.xml, so the build is fast and the sitemap is exhaustive. HackTricks, mdBook-rendered books, and Material-themed docs land here. Multi-language wikis are auto-filtered to English when more than 40% of paths cluster under language codes.
• gitbook — for GitBook-rendered books, including custom domains. They also publish sitemap.xml, but some custom GitBook deployments do not, so a Tier-2 Playwright nav harvest is the documented fallback. ired.team and Practical CTF are typical examples.
• github-repo — for markdown-based knowledge bases hosted on GitHub (PayloadsAllTheThings, awesome-* lists, OWASP guides). The sitemap is the recursive Git tree, filtered to text formats (.md, .txt, .rst). Big repos may be marked truncated by GitHub — the resource is then saved with an explicit _error field. Anonymous GitHub API is rate-limited to 60 req/h, so adding a GitHub token in API Keys is recommended; the per-resource token override is the per-repo escape hatch.
• cve-poc-db — for CVE-indexed PoC repos (trickest/cve, 0xMarcio/cve, nomi-sec/PoC-in-GitHub). The repo has hundreds of thousands of files, so enumerating the tree is wasteful. Instead, the lookup path is built deterministically from the CVE-ID: contents/{year}/CVE-YYYY-NNNNN.md. The agent must pass cve_id="CVE-YYYY-NNNNN"; the tool docstring tells the agent so explicitly. Falls back to listing /contents/{year} and substring-matching on miss.
• sphinx-docs — for Sphinx, Read the Docs, and Docusaurus sites. They ship a structured searchindex.json with docnames[] and titles[], which is the perfect shape for a sitemap. Tool documentation (Scapy, Volatility 3, Mitmproxy, Sliver C2) is the canonical use case. Cache TTL is longer (14 days) because tool docs change rarely.
• agentic-crawl — the fallback for anything that did not match the five deterministic detectors: personal blogs, custom CMS, vendor research portals without a published sitemap. A bounded LLM loop drives Playwright over the site, asking Claude on each page which links to follow next. This is the only type that pays a real LLM cost at verify time (typically $0.30 to $0.60 with Sonnet) and the only type that blocks for ~90-180 seconds on add. Once verified, the sitemap is just JSON in the database and query-time stays sub-second.

A site can change type on Refresh. Detection runs every time. If a wiki migrates from MkDocs to Docusaurus, hitting Refresh on the card swaps the badge from mkdocs-wiki to sphinx-docs and rebuilds the sitemap with the right strategy.

What the agent sees

When you start (or reload) a project, the agent reads your enabled resources and dynamically composes the description for the tradecraft_lookup tool. Each enabled resource appears in the docstring as one block:

hacktricks   (mkdocs-wiki) https://book.hacktricks.wiki
  Comprehensive offensive security wiki. Covers web (XSS, SSRF,
  SSTI, deserialization), Active Directory (Kerberoasting, DCSync,
  golden ticket, ADCS), Linux/Windows privesc, cloud, container
  escapes... [your saved 250-350 word summary]

The whole "which resource fits this query" decision is made by the model reading these summaries. There is no vector router and no learned retrieval. The summary you saved at add-time is the routing intelligence — write good summaries (or trust the LLM-generated default) and the agent will pick the right resource on its own.

When zero resources are enabled, the entry is removed from the tool registry entirely, so the agent does not see a tool that promises a capability it cannot deliver.

Tunables (per-project)

The agentic-crawl loop and the cache layer expose four knobs in the project's Project Settings under the agent block (TRADECRAFT_*):

Plus three runtime knobs:

MCP Tool Plugins

Plug any Model-Context-Protocol (MCP) server into the agent as a tool plugin — Shodan, GitHub, Burp Suite, Censys, your own internal tools — without editing code, rebuilding containers, or running migrations. Every tool the plugin exposes auto-appears in every project's Tool Matrix with phase toggles.

Two paths to add a plugin:

• Quick add — pick from 39 prefilled preset cards (DeepWiki, GitHub, Hugging Face, Shodan, VirusTotal, Censys, mitmproxy, Burp Suite, …). Click → form opens prefilled with everything except your API key.
• Add MCP (red button, top right) — manual form for custom / internal MCPs. Three transports supported: stdio (subprocess), streamable_http (recommended HTTP), sse (legacy HTTP).

Each saved plugin's tools are auto-injected into the agent's system prompt within ~1 second of Save. The orange Discover and add new tools button on the form runs a live MCP list_tools() against your draft and auto-imports the discovered tool list into your form — names, descriptions, and JSON-schema-derived args_format all populated automatically.

Full operator manual — every form field, every preset, the auth flow, the discovery workflow, the validation rules, troubleshooting, and the storage / security model: see the MCP Tool Plugins wiki page.