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 agentmods add commands/awarexone/agentic-bug-hunter/nosqligit clone --depth 1 https://github.com/Awarexone/Agentic-Bug-HunterWrote 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/commands/awarexone/agentic-bug-hunter/nosqli)<a href="https://agentmods.dev/commands/awarexone/agentic-bug-hunter/nosqli"><img src="https://agentmods.dev/badge/commands/awarexone/agentic-bug-hunter/nosqli.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
nosqli 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 4d 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.
What it actually says
/nosqli
Test JSON/operator-style NoSQL injection — the "db" attack surface web2 SQLi
tools miss. Turns an equality check ({user: X, pass: Y}) into "match anything"
via operator injection → auth bypass / data read.
Usage
/nosqli --login https://t/api/login --user-field email --pass-field password
/nosqli --login https://t/api/login --baseline-user [email protected] --baseline-pass wrong
/nosqli --query "https://t/api/items?id=1"
Run directly:
tools/nosqli_scanner.py --login https://t/api/login \
--user-field email --pass-field password --json
Techniques
| Technique | Payload | Confirms via |
|---|---|---|
| Operator auth-bypass | {"email":{"$ne":null},"password":{"$ne":null}} |
response flips 401→200 / body-length jump |
| Known-user wildcard | {"email":"admin","password":{"$ne":""}} |
same |
$regex match-all |
{"$regex":".*"} |
same |
| Bracket-syntax (Express/qs) | email[$ne]=&password[$ne]= |
manual diff (emitted) |
$where time-based blind |
{"$where":"sleep(5000)"} |
response delay ≥ 3.5s |
How detection works
The scanner sends a wrong-credential baseline first, then each payload, and flags a finding when:
- status flips from 401/403 to 200/302, or
- body length changes by >25% (or >64 bytes) at the same status, or
- the
$wheresleep payload measurably delays the response (server-side JS eval = CRITICAL).
--query mode can't auto-confirm (no baseline), so it prints the bracket-
injection variants for you to diff manually in Burp/Repeater.
Impact
Operator auth-bypass on a login = account takeover / full auth bypass
(Critical). $where injection = server-side JS execution → often RCE-adjacent.
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.
- 4d ago First seen · 51 lines · 0 tokens per session scan A ab578f77f90b
nosqli is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,689 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 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-30.
Other commands, from other repositories
recon
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.
hunt
Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt .target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome].
token-scan
Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].
autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].
triage
Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.