Warden Service

Query Warden Service with a read-only personal token and return a bounded, evidence-based answer.

Workflow

1. Identify the Warden Service origin and confirm WARDEN_PAT is set without displaying its value.
2. If the token is missing, direct the user to API access in the Warden Service dashboard. Have them create a personal token and export it as WARDEN_PAT; never ask them to paste it into chat or a command literal.
3. Read references/read-api.md to select the exact route, supported filters, pagination behavior, and response fields for the question.
4. Narrow the request to the user's repository, time range, skill, severity, or other stated scope. Use a bounded limit for runs and findings.
5. Send a GET request with the token read from the environment. URL-encode every query value.
6. Follow nextCursor only while more results are needed. Preserve all original filters and stop when the requested scope is satisfied or the response omits nextCursor.
7. Summarize the relevant JSON fields. State the route and filters used, and distinguish an empty result from a failed request.

Request Pattern

Use --get with --data-urlencode instead of assembling a query string manually: