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 skills/mahuttha/offensive-recon/sqlmap-scannpx skills add mahuttha/offensive-recon --skill sqlmap-scangit clone --depth 1 https://github.com/mahuttha/offensive-reconWrote 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/mahuttha/offensive-recon/sqlmap-scan)<a href="https://agentmods.dev/skills/mahuttha/offensive-recon/sqlmap-scan"><img src="https://agentmods.dev/badge/skills/mahuttha/offensive-recon/sqlmap-scan.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.00043 | $0.01154 |
| Opus 5 | $0.00022 | $0.00577 |
| Sonnet 5 | $0.00009 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
sqlmap-scan 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 3d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- If sqlmap not found: "SQLMap is not installed. Install with: `sudo apt install sqlmap`" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQLMap Scan — SQL Injection Detection
Test for SQL injection vulnerabilities using SQLMap against an authorized target.
Decision Loop: In-the-Loop (STRICT — target + mode approval required)
Safety — CRITICAL Legal Warning
Before ANY execution, display this warning:
⚠️ คำเตือนทางกฎหมาย (Legal Warning)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SQL injection testing without explicit written authorization is ILLEGAL
in most jurisdictions. SQLMap actively sends malicious payloads to the target.
ยืนยัน (Confirm):
1. คุณได้รับอนุญาตให้ทดสอบเป้าหมายนี้แล้ว (You have authorization to test this target)
2. เป้าหมาย: <target-url>
3. โหมด: <mode>
ดำเนินการต่อ? (Proceed?) [y/N]
Do NOT proceed without explicit user confirmation.
Arguments
Parse the user's input for:
<target-url>— URL with parameters (e.g.,http://target.com/page?id=1) (REQUIRED)--mode— Test mode (default:detect)--risk— Risk level 1-3 (default: 1)--level— Test level 1-5 (default: 1)
Scan Modes
| Mode | Flags | Description |
|---|---|---|
detect |
--batch --smart |
Detect injectable parameters only |
enumerate |
--batch --dbs |
Enumerate databases after detection |
dump |
--batch --dump -D <db> -T <table> |
Dump table data (REQUIRES extra confirmation) |
Execution
After user confirmation, run:
# Build command based on mode
case "<mode>" in
detect)
sqlmap -u "<target-url>" --batch --smart --risk <risk> --level <level> \
--output-dir=/tmp/sqlmap-output --forms 2>&1 | tee /tmp/sqlmap-console.txt
;;
enumerate)
sqlmap -u "<target-url>" --batch --dbs --risk <risk> --level <level> \
--output-dir=/tmp/sqlmap-output 2>&1 | tee /tmp/sqlmap-console.txt
;;
dump)
# REQUIRES ADDITIONAL CONFIRMATION for data extraction
sqlmap -u "<target-url>" --batch --dump -D <db> -T <table> \
--output-dir=/tmp/sqlmap-output 2>&1 | tee /tmp/sqlmap-console.txt
;;
esac
Output Format
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.
- 3d ago First seen · 128 lines · 43 tokens per session scan A 8a5cd3b589e2
sqlmap-scan is a skill published in the GitHub repository mahuttha/offensive-recon (4 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 1,154 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…