Terminal
Terminal/Skill
Queries the Warden Service read API to inspect, search, summarize or export runs, findings, costs and repositories using a read-only token.
By Sentry
Works with
npx skills add getsentry/warden --skill warden-serviceQuery Warden Service with a read-only personal token and return a bounded, evidence-based answer.
WARDEN_PAT is set without displaying its value.WARDEN_PAT; never ask them to paste it into chat or a command literal.references/read-api.md to select the exact route, supported filters, pagination behavior, and response fields for the question.limit for runs and findings.GET request with the token read from the environment. URL-encode every query value.nextCursor only while more results are needed. Preserve all original filters and stop when the requested scope is satisfied or the response omits nextCursor.Use --get with --data-urlencode instead of assembling a query string manually:
curl --fail-with-body --silent --show-error --get \
-H 'Accept: application/json' \
-H "Authorization: Bearer ${WARDEN_PAT}" \
--data-urlencode 'severity=high' \
--data-urlencode 'skill=security-review' \
--data-urlencode 'limit=30' \
"${WARDEN_SERVICE_URL%/}/api/v1/findings"
Keep the token in WARDEN_PAT. Do not enable verbose or trace output that could expose the authorization header.
Only /api/v1/runs and /api/v1/findings use cursor pagination. Treat nextCursor as opaque and pass it back unchanged through URL encoding:
curl --fail-with-body --silent --show-error --get \
-H 'Accept: application/json' \
-H "Authorization: Bearer ${WARDEN_PAT}" \
--data-urlencode "cursor=${NEXT_CURSOR}" \
--data-urlencode 'severity=high' \
--data-urlencode 'limit=100' \
"${WARDEN_SERVICE_URL%/}/api/v1/findings"
Use the HTTP status and the JSON error.code and error.message together:
| Status | Meaning | Action |
|---|---|---|
| 400 | Invalid query filters | Correct the parameter names, values, or RFC 3339 timestamps. |
| 401 | Missing, invalid, or expired authentication | Verify the origin and replace the personal token through API access. |
| 403 | Insufficient role or disallowed personal-token operation | Keep the request read-only and within the token's repository scope. |
| 404 | Unknown or unauthorized route/resource | Verify the documented route or ID without assuming the resource exists. |
| 429 | Rate limited | Wait and retry later; do not create a tight retry loop. |
GET or HEAD. Never attempt POST, PUT, PATCH, or DELETE with them.references/read-api.md.