modules

Reqlore module pages

One reference page per panel. Every page follows the same shape so you can predict where to look:

1. Purpose — what task it really solves.
2. Where it is — URL, nav location, accesskey to reach it.
3. Quick start — minimum-viable usage in 5 numbered steps.
4. The interface — every visible field and button on the page.
5. How it integrates — Send-to producers and consumers.
6. Engines — which of the six request engines apply.
7. Keyboard map — every accesskey on the page + relevant globals.
8. Accessibility notes — read order, ARIA roles, AAA-specific patterns.
9. Recipes — 3-6 worked examples with real syntax.
10. Troubleshooting — known gotchas.
11. CLI equivalents (where any).
12. Storage footprint — what gets persisted into the .rlr and under what key.

Index

Core

• dashboard.md
• proxy.md
• history.md
• search.md
• sitemap.md

Attack workbenches

• repeater.md
• intruder.md
• param-miner.md
• scanner.md
• dom-hunter.md
• comparer.md
• decoder.md
• jwt.md

Specialist workbenches

• graphql.md
• websocket.md
• saml.md
• poc.md
• macros.md
• sequencer.md
• oast.md
• h2.md
• smuggling.md
• scheduler.md

Plumbing

• matchreplace.md
• reporter.md
• plugins.md
• cues.md
• settings.md
• help.md