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 sanjaysaini1952/BugBounty-Arsenal --skill idorgit clone --depth 1 https://github.com/sanjaysaini1952/BugBounty-ArsenalWrote 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/sanjaysaini1952/bugbounty-arsenal/idor)<a href="https://agentmods.dev/skills/sanjaysaini1952/bugbounty-arsenal/idor"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/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/sanjaysaini1952/bugbounty-arsenal/idor"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/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.00000 | $0.00713 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
idor scanned grade A with 0 findings 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDOR / BAC Hunting Skill — 15 Test Cases
Load when: IDOR, BAC, broken access control, unauthorized access, horizontal privilege escalation.
56. Sequential ID enumeration (easy)
For every entity the app returns (orders, users, files, profiles), iterate IDs (/api/v1/2, /api/v1/3, ...). Report any accessible resources belonging to another user without authentication changes.
57. IDOR via UUID prediction (medium)
If IDs are UUIDs, check if they are sequential, time-based (v1), or predictable (v4 from weak RNG). If so, enumerate.
58. IDOR via parameter removal (easy)
Remove all authorization headers/cookies. Try ?admin=true, ?userId=current&target=other, ?role=admin. Report any response differences.
59. BAC on hidden API endpoints (medium)
Map the API surface: check JS source, swagger, docs. Test each endpoint with and without auth tokens. Report any endpoint that accepts unauthenticated requests.
60. IDOR in file downloads (easy)
Change file IDs, file paths, or query parameters when downloading files. Test path traversal in filenames (../../../etc/passwd).
61. Horizontal privilege escalation (medium)
Create two user accounts. Perform actions on account A, then replay the same request with account B's cookies/headers. Report any data leak or state change.
62. Vertical privilege escalation (easy)
Create user and admin accounts. Replay user-level admin requests with admin cookies. Report any endpoint accessible to both roles without proper checks.
63. IDOR via JSON body manipulation (easy)
Change {"userId": 1} to {"userId": 2} in POST/PUT requests. If the app uses the body for authorization, report.
64. IDOR in batch operations (medium)
If API supports batch requests (multiple IDs in one call), mix your IDs with other users' IDs. Report cross-user data returned in batch.
65. IDOR via GraphQL (hard)
In GraphQL queries, replace node IDs in node(id: "...") with other users' nodes. Report any data returned.
66. BAC on admin endpoints (easy)
Try accessing /admin, /dashboard, /api/admin/users without auth. Check response codes and content.
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.
- 12d ago First seen · 58 lines · 0 tokens per session scan A 8ad3924156d4
idor is a skill published in the GitHub repository sanjaysaini1952/BugBounty-Arsenal (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 713 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.