Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed travel-research skill that sends accommodation search data to Crawlora, with no evidence of booking actions, account changes, persistence, or privilege escalation.
Install only if you are comfortable sending travel-search inputs and your Crawlora API key to Crawlora. Keep the key secret, avoid submitting payment data or unrelated personal information, and be aware that Vrbo is supported even though the short manifest description omits it.
The manifest describes a limited travel-research skill for Airbnb, Agoda, Hotels.com, and Trip.com, but the body adds VRBO workflows and deeper review/property/rate lookups not disclosed in the declared purpose. This description-behavior mismatch can bypass reviewer and user expectations, causing the skill to access additional data surfaces and perform broader collection than was authorized or understood.
The skill invokes shell commands (scripts/crawlora.sh) but does not declare an explicit tool scope such as permissions or allowed-tools. That omission weakens least-privilege controls and makes it easier for a caller or future edit to expand shell-based behavior beyond the intended research workflow without clear policy boundaries.
This skill is designed around external transmission to api.crawlora.net, so network egress is expected; however, it still represents a real security/privacy boundary because user-supplied travel queries, property identifiers, dates, and related metadata leave the local system. The travel-research context lowers severity because the endpoints are read-oriented and non-transactional, but outbound data flow to a third party should still be disclosed and controlled.
Endpoints this skill uses, grouped by platform. Call them via `scripts/crawlora.sh` (see SKILL.md).
All paths are relative to the API base `https://api.crawlora.net/api/v1` and require the header `x-api-key: $CRAWLORA_API_KEY`. Path params like `{id}` are substituted into the URL; `GET` params go in the query string; `POST` params go in a JSON body.
**31 endpoints across 5 platform group(s).**
The file explicitly instructs use of an API key header for outbound requests but provides no warning about credential sensitivity, transmission to a third-party service, or safe handling expectations. In an agent setting, this increases the risk of unintended secret exposure, unsafe logging, or users being unaware that their queries and identifiers are sent to an external aggregator.
The manifest says the skill compares listings across Airbnb, Agoda, Hotels.com, and Trip.com, but this endpoint reference documents an additional fifth platform, Vrbo. That expands the skill's stated coverage beyond the manifest's described scope, indicating a description-to-behavior mismatch.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
# Usage:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
# Crawlora REST helper — minimal, dependency-free (curl only).
# Calls https://api.crawlora.net/api/v1 with your Crawlora API key.
# Get a free key (2,000 credits/mo, no card) at https://crawlora.net?utm_source=github&utm_medium=referral&utm_campaign=crawlora-skills.
#
# Usage:
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# config supplies the header and is removed automatically on exit.
umask 077
curl_config="$(mktemp "${TMPDIR:-/tmp}/crawlora-curl.XXXXXX")"
chmod 600 "$curl_config"
trap 'rm -f "$curl_config"' EXIT
printf 'header = "x-api-key: %s"\n' "$CRAWLORA_API_KEY" >"$curl_config"
auth=(--config "$curl_config")
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
[ -n "$body" ] || body='{}'
# Stream the body on stdin so curl never interprets a user value as its
# @file shorthand (and cannot read local files supplied in a request body).
printf '%s' "$body" | curl -q -fsS -X "$method" "${auth[@]}" \
-H "Content-Type: application/json" --data-binary @- "${base}${path}"
fi
The documentation introduces VRBO discovery, quote, and review workflows that are absent from the manifest description, expanding operational scope after the initial declaration. Even if the added behavior remains research-only, undisclosed scope increases the risk of hidden capability creep and reduces the effectiveness of trust and approval processes.
This markdown file describes what the skill uses and how to call its endpoints, but it does not provide any explicit trigger phrases, invocation boundaries, or negative examples. In a manifest/markdown context, that omission can make activation conditions overly broad or unclear, increasing the chance of unintended invocation.