hunt-api-abuse

Validates server-side quota and cost controls on API endpoints through evidence-gated probes.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-api-abuse-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-api-abuse
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-api-abuse
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-api-abuse-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? APIs often lack enforced server-side limits on pagination, batch operations, exports, search complexity, and async jobs, leaving them open to resource abuse. This Skill provides a disciplined, authorization-gated workflow to verify whether those quota and cost controls actually exist, without performing denial-of-service testing. ## Core Features & Use Cases - Evidence-Gated Validation: Follows a fixed baseline → single-variable probe → post-baseline → oracle → evidence pipeline so every finding is backed by observable server behavior. - Abuse Surface Coverage: Targets pagination limits, batch sizes, GraphQL complexity hints, export jobs, search endpoints, and async task queues using only self-owned accounts and test data. - Strict Stop Conditions: Halts immediately on third-party data exposure, shared infrastructure impact, or irreversible side effects, and routes specialized cases to ReDoS, GraphQL, or rate-limit skills. - Use Case: During an authorized assessment, you suspect an export endpoint accepts arbitrarily large batch requests. Use this Skill to plan minimal no-op probes that compare server acceptance against documented quotas and record the evidence. ## Quick Start Use $hunt-api-abuse to plan an evidence-gated, authorized validation of quota controls on my API's batch and export endpoints.

Frequently Asked Questions about hunt-api-abuse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test API rate limits and quotas without causing downtime?

Use minimal single-variable probes with your own accounts and no-op requests, comparing server acceptance against documented quotas. Establish baseline request costs first, avoid concurrency and long-running tasks, and stop immediately on any queue, CPU, or error-rate anomaly.

What API endpoints should be checked for resource abuse vulnerabilities?

Focus on pagination limits, batch endpoints, export jobs, search endpoints with filter complexity, GraphQL query complexity, and asynchronous task queues. These are the surfaces where missing server-side quotas create cost and abuse exposure.

Does this API abuse testing perform denial-of-service attacks?

No. The workflow explicitly prohibits DoS: it uses only minimal numbers of low-cost, self-owned requests within approved rate windows. Any concurrency, wide queries, or actual large downloads are out of scope, and anomalies trigger immediate stops.

What counts as a confirmed API quota vulnerability versus a false positive?

A valid finding requires the server to accept self-owned low-cost requests beyond stated limits with observable undue cost or missing quota controls. Client-side throttling, network latency, or a single 429 response do not qualify and are marked inconclusive.

What authorization is needed before testing API abuse controls?

You need written approval defining the testing window, scope, host and identity baselines, rate limits, stop thresholds, and a recovery owner. Testing uses only your own accounts, objects, domains, and test data.