Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ShulkwiSEC/bb-huge --skill bola-idorgit clone --depth 1 https://github.com/ShulkwiSEC/bb-hugeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/shulkwisec/bb-huge/bola-idor)<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/bola-idor"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/bola-idor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/bola-idor"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/bola-idor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00107 | $0.01863 |
| Opus 5 | $0.00053 | $0.00932 |
| Sonnet 5 | $0.00021 | $0.00373 |
| Haiku 4.5 | $0.00011 | $0.00186 |
Grade A, and why
bola-idor scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Designed for Claude Code. Burp Suite (Autorize extension) or curl recommended. How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broken Object Level Authorization (BOLA / IDOR)
What Is Broken and Why
The server accepts a resource identifier from the client and fetches the object without verifying the requesting user owns or has access to it. Authorization is enforced at the route level ("is this user logged in?") but not at the object level ("does this user own object 1042?"). An attacker substitutes their identifier for a victim's to read, modify, or delete resources they should never access. BOLA is consistently the #1 OWASP API Security risk because it is trivial to test and almost always yields high-severity findings.
Key Signals
- Numeric or sequential IDs in URL path:
/api/orders/1042,/users/7/profile - UUIDs or hashes in query params or body referencing another user's object
- Parameters named
user_id,account_id,owner_id,ref,target_id,invoice - Write operations (PUT/PATCH/DELETE) accepting an object ID
- Export/download/share endpoints with a resource ID parameter
- Keywords
meorcurrentused as ID aliases — swappable for integer IDs - Older API versions still accessible:
/v1/,/v2/,/legacy/ - UUIDs discoverable via public profiles, share links, password reset flows, Wayback Machine
Methodology
- Map all object identifiers across the entire app — URLs, query params, request body, cookies, headers.
- Create two accounts with distinctive names (e.g.
attacker_a,victim_b). Use separate browsers to keep sessions fully isolated. Fully populate the victim account with varied resources and document all encountered IDs. Capture all requests with the victim session. - Replay each request using the attacker token with the victim's object IDs.
- Compare responses — same data returned = BOLA confirmed.
- Test unauthenticated: remove
Authorizationheader entirely. - Test write operations (PUT/PATCH/DELETE) — impact is higher than reads.
- Test indirect references: export endpoints, share links, scheduled jobs, email triggers.
- Test less-visible features: auto-save, draft, notification, audit log, attachment endpoints.
- Try older API versions (
/v1/,/beta/) which often lack access control patches. - For second-order IDOR: store a payload referencing victim's ID, trigger async processing, observe outcome.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 155 lines · 107 tokens per session scan A 01c60b97fb2b
bola-idor is a skill published in the GitHub repository ShulkwiSEC/bb-huge (22 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,863 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
hunt-api-misconfig
Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {isadmin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this…
octopus-architecture
Review system architecture, simplify boundaries, or compare interface designs from repository evidence.
agenticx-a2a-connector
Guide for using the A2A (Agent-to-Agent) communication protocol in AgenticX including agent discovery, skill invocation, remote agent cards, and distributed agent systems. Use when the user wants agents to communicate with each other, set up distributed agent systems, invoke remote agent skills, or build…
agenticx-tool-creator
Guide for creating custom tools in AgenticX including function decorator tools, MCP tool integration, tool registries, and remote tool access. Use when the user wants to create tools for agents, integrate external APIs as tools, build MCP servers, or extend agent capabilities with custom functions.
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
pwn-ai-openai
Drive PWN::AI::OpenAI from pwneval.