Capability catalog and tools

An extension never chooses binaries, arguments or images. It requests a typed capability and the CatBridge supervisor builds the command, reserves the budget and returns only verified JSON. Each capability has an executor pinned by version and hash; modifying the executable invalidates approved capabilities.

Initial capabilities (SDK 1.3) #

Ecosystem capabilities (SDK 1.4) #

The stage 2 to 5 adapters require contract 2 and .catflow 5. API v1 and the signed Protocol 2 stay compatible.

Some profiles query selected public sources: subfinder uses crt.sh and CertSpotter; Uncover uses Shodan InternetDB by IP, with no credentials; gau and waybackurls use the Wayback Machine — historical URLs do not prove active services. DNS accepts A, AAAA, CNAME, MX, NS and TXT; TTL and DNSSEC are not considered verified.

Execution profiles #

• read-only — offline operations and DNS lookups.
• external-approved — queries to approved external sources.
• active-approved — active tests against approved destinations.
• mutation-approved — Schemathesis only, after you explicitly select the operations and obtain a new approval.

In the ecosystem, HTTP is limited to GET. Discoveries and redirects do not widen the scope.

Budgets and limits #

Limits apply to the whole task and are reserved before each batch:

Cancellation does not return a reservation whose consumption is unknown. Completed batches (up to five destinations and five templates) are reused; repeating a batch with an unknown result requires an explicit choice.

Reviewed templates (Nuclei) #

The manifest is a list of id, path, sha256 and name in pt-BR/en. Update the hash only after you review the YAML.

{
  "templates": [
    {
      "id": "aurora-cache",
      "path": "examples/aurora-cache.yaml",
      "sha256": "…",
      "name": {"pt-BR": "Cache do Aurora", "en": "Aurora cache"}
    }
  ]
}

Only HTTP GET/HEAD, {{BaseURL}}-based targets, matchers and extractors are accepted. Code, executable JavaScript, headless, DNS, OAST, external workflows, raw requests and configured redirects are not accepted. Headers that change host or framing are refused. Hashes are verified before each run.

Data the tool receives #

• The default endpoints-only profile does not forward cookies, tokens or bodies.
• selected-headers shares up to 16 headers / 16 KiB explicitly chosen in the step and included in the approval.
• Cookie and Authorization require explicit selection and SECRET classification; host/framing headers are refused.
• Selected values live in a private temporary file removed when the task ends. Bodies are never sent to Nuclei.

Resources sent to the workflow #

Some adapters use resources you upload in signed chunks of up to 64 KiB, bound to device, flow, revision and classification; the hash is part of the immutable approval.

Absolute paths, directory traversal and symbolic links are refused.

Results and evidence #

Results arrive in signed pages of up to 50 records or 512 KiB, with verifiable receipts, versions and hashes of the executable and templates. Credential values and parameters recognized as secret are hidden.

Next step #

• Install and pair CatBridge
• Visual workflows
• Error reference