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 aws-iam-enumgit 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/aws-iam-enum)<a href="https://agentmods.dev/skills/purpleailab/decepticon/aws-iam-enum"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/aws-iam-enum/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/aws-iam-enum"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/aws-iam-enum.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.00025 | $0.00724 |
| Opus 5 | $0.00013 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
aws-iam-enum 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aws-iam-enum — 86% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS IAM Enumeration + Privesc
1. Identity check
aws sts get-caller-identity
aws iam get-account-summary
2. Attached policies
aws iam list-attached-user-policies --user-name ME --output json > /tmp/attached.json
aws iam list-user-policies --user-name ME --output json > /tmp/inline.json
aws iam list-groups-for-user --user-name ME --output json > /tmp/groups.json
For each attached policy ARN:
aws iam get-policy --policy-arn ARN --query 'Policy.DefaultVersionId'
aws iam get-policy-version --policy-arn ARN --version-id VID > /tmp/policy.json
Then:
iam_policy_audit(open("/tmp/policy.json").read())
3. Check each privesc primitive
Rhino Security's canonical 21 paths — any Allow on these is a chain step:
- iam:CreateAccessKey (other user)
- iam:CreateLoginProfile
- iam:UpdateLoginProfile
- iam:AttachUserPolicy / iam:AttachGroupPolicy / iam:AttachRolePolicy
- iam:PutUserPolicy / iam:PutGroupPolicy / iam:PutRolePolicy
- iam:CreatePolicyVersion (if SetAsDefault=true)
- iam:SetDefaultPolicyVersion
- iam:PassRole + lambda:CreateFunction + lambda:InvokeFunction
- iam:PassRole + ec2:RunInstances
- iam:PassRole + ecs:RunTask / UpdateService
- glue:CreateDevEndpoint / UpdateDevEndpoint
- cloudformation:CreateStack with iam:PassRole
- datapipeline:CreatePipeline
- lambda:UpdateFunctionCode (existing function with priv role)
- iam:AddUserToGroup
- iam:UpdateAssumeRolePolicy
- iam:CreateRole + sts:AssumeRole
- codebuild:CreateProject with iam:PassRole
- sagemaker:CreateTrainingJob with iam:PassRole
- aws-marketplace:Subscribe (rare, but noted)
- sts:AssumeRole (direct)
4. Graph promotion
kg_add_node(kind="vulnerability", label="IAM:CreateAccessKey → account takeover", props={"severity":"critical","source":"aws-iam"})
kg_add_node(kind="crown_jewel", label="AWS Account 1234")
kg_add_edge(src=<vuln>, dst=<crown_jewel>, kind="grants", weight=0.3)
5. Common chains
- Dev user has
iam:PassRole+lambda:CreateFunction+ a Lambda role with admin → create malicious Lambda → assume admin iam:UpdateLoginProfile+sts:GetFederationToken→ temporary console access as another user
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 · 74 lines · 25 tokens per session scan A ea41fcf849b6
aws-iam-enum is a skill published in the GitHub repository PurpleAILAB/Decepticon (5,471 stars, last pushed 10d ago), licensed Apache-2.0. It adds 25 tokens to every session and 724 once invoked, about $0.0001 per session on Opus 5. 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-09-03.
Other skills, from other repositories
implementing-zero-trust-network-access-with-zscaler
Use when implement Zero Trust Network Access using Zscaler Private Access (ZPA) to replace traditional VPN with identity-based, context-aware access to private applications through the Zscaler Zero Trust Exchange. Use when implementing zero trust network access using zscaler private access (zpa).
implementing-zero-trust-with-beyondcorp
Use when deploy Google BeyondCorp Enterprise zero trust access controls using Identity-Aware Proxy (IAP), context-aware access policies, device trust validation, and Access Context Manager to enforce identity and posture-based access to GCP resources and internal applications. Use when deploying google beyondcorp…
analyzing-ethereum-smart-contract-vulnerabilities
Use when perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet. Use when performing static and symbolic analysis of solidity smart contracts using.
analyzing-azure-activity-logs-for-threats
Use when queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity…
analyzing-cloud-storage-access-patterns
Use when detect abnormal access patterns in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics. Identifies after-hours bulk downloads, access from new IP addresses, unusual API calls (GetObject spikes), and potential data exfiltration using statistical…
prometheus-configuration
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.