Borrowing it
Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/idor-pentest/SKILL.mdgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote 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/suzu-testing/metasploit-cursor-harness/idor-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/idor-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/idor-pentest/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/suzu-testing/metasploit-cursor-harness/idor-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/idor-pentest.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.00046 | $0.01921 |
| Opus 5.5 | $0.00018 | $0.00768 |
| Sonnet 5.5 | $0.00009 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
idor-pentest scanned grade A with 2 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 1mo 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X PUT -H "Authorization: Bearer <user_b_token>" -d '{"email":"[email protected]"}' "http://<target>/api/users/<user_a_id>" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer <token_b>" "http://<target>/api/orders/1001" How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insecure Direct Object References Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE). - Load
web-app-pentestfor overall web testing context. - Requires two test accounts: same-role (horizontal) and different-role (vertical).
Triggers
- Predictable numeric or sequential IDs in URLs, query params, or JSON bodies
- UUID/GUID or MongoDB ObjectId references in API requests
- User can access own resources by ID but authorization on ID swap is unclear
- Horizontal privesc (peer data) or vertical privesc (admin-only objects)
- BOLA/BFLA patterns in REST or GraphQL APIs
Workflow
Task Progress:
- [ ] Capture authenticated requests referencing object IDs
- [ ] Swap IDs across accounts/roles; test increment, decrement, encoding variants
- [ ] Try wildcard, parameter pollution, and HTTP method/content-type changes
- [ ] Confirm unauthorized read, modify, or delete with two distinct test accounts
- [ ] Document with request/response evidence showing cross-account access
Detection
Numeric ID swapping
CLI (primary for web vulns):
ffuf -u "http://<target>/api/orders/FUZZ" -w ids.txt -H "Authorization: Bearer <token>" -mc 200
curl -H "Authorization: Bearer <token_b>" "http://<target>/api/orders/1001"
Test: /api/orders/1001 (User A) with User B token.
MSF MCP: No direct module. Use msf_search_modules(query="authorization") or msf_search_modules(query="idor").
Increment/decrement fuzzing
CLI (primary):
ffuf -u "http://<target>/api/users/FUZZ" -w <(seq 1 5000) -H "Cookie: session=<token>" -mc 200,403
# pwsh (Windows):
1..5000 | ForEach-Object { Invoke-WebRequest "http://<target>/api/users/$_" -Headers @{Authorization="Bearer <token>"} }
for i in $(seq 99 105); do curl -s -o /dev/null -w "$i:%{http_code}\n" "http://<target>/api/doc/$i" -H "Authorization: Bearer <token>"; done
Leading zeros: /order_id=00001001
MSF MCP: No direct module.
Exploitation by variant
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.
- 1mo ago First seen · 222 lines · 46 tokens per session scan A f7379231cfb3
idor-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,921 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…