competition-mailbox-abuse — Claude Code skill: what it does
competition-mailbox-abuse — a skill for Claude Code and other environments specializing in analyzing enterprise mail abuse within CTF sandboxes.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a claude-codeWhat competition-mailbox-abuse does
This skill tracks suspicious activity in mail systems, including OAuth consent, forwarding rules, delegate access, and transport configurations. It structures evidence by linking message IDs, tokens, and user actions into a coherent exploitation chain.
Operation requires $ctf-sandbox-orchestrator to be active first to establish sandbox assumptions, node ownership, and evidence priorities. The skill correlates sign-in logs, inbox rules, transport settings, and mailbox audit events to reproduce the attacker's path.
It is recommended to load references/mailbox-abuse.md for access to consent and rule checklists. The skill focuses on mail artifacts, so if the task shifts to host pivots or Kerberos authentication, switch back to broader identity tools.
What it helps with
- trace phishing chains to OAuth consent grants
- identify forwarding rules in compromised mailboxes
- link access tokens to specific mailbox actions
- prove unauthorized delegate access
Example prompts for the agent
- Analyze the chain from OAuth consent to mail forwarding for [email protected].
- Map the exploitation path through transport rules based on these logs.
- Find the connection between the access token and mailbox delegation.
How to install competition-mailbox-abuse
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a claude-code2Manually: put the files in place
~/.claude/skills/competition-mailbox-abuse/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-mailbox-abuse/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a codex2Manually: put the files in place
.agents/skills/competition-mailbox-abuse/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a cursor2Manually: put the files in place
.cursor/skills/competition-mailbox-abuse/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-mailbox-abuse/SKILL.md2Manually: put the files in place
.github/skills/competition-mailbox-abuse/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-mailbox-abuseManually: put the files in place
.devin/skills/competition-mailbox-abuse/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-mailbox-abuse
How to install competition-mailbox-abuse in Claude Code?
Run the command npx skills add zhaoxuya520/reverse-skill --skill competition-mailbox-abuse -a claude-code in your project terminal.
What does competition-mailbox-abuse do?
It automates the analysis of mail abuse in CTF environments, helping to find and document exploitation chains related to mail rules, OAuth tokens, and delegate permissions.
What is required to use competition-mailbox-abuse?
You must have $ctf-sandbox-orchestrator running, as it establishes the necessary sandbox assumptions before this skill can function.
Source text
SKILL.md · MIT
--- name: competition-mailbox-abuse description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for enterprise mail abuse, OAuth consent, inbox or forwarding rules, transport rules, shared mailbox access, phishing chains, and token-to-mailbox side effects. Use when the user asks to trace mailbox rules, OAuth consent grants, forwarding or delegate abuse, shared mailbox access, message-trace evidence, or explain how mail artifacts turn into persistence, exfiltration, or privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Mailbox Abuse Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the decisive path runs through mailbox behavior, consent flow, or message-routing effects rather than generic AD evidence alone. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Decide whether the active path is phishing-to-consent, token-to-mailbox, rule-based persistence, or transport-level mail rerouting. 2. Keep mailbox evidence, identity evidence, and message-trace evidence tied to the same user, mailbox, token, or message ID. 3. Separate possession of a token or delegate edge from the actual mailbox effect it enables. 4. Record forwarding targets, rule predicates, consent scopes, shared mailbox edges, and resulting mail flow in compact blocks. 5. Reproduce the smallest mail effect that proves persistence, exfiltration, or privilege. ## Workflow ### 1. Map The Mail Trust Path - Identify the principal, mailbox, token or session, consent grant, delegate edge, shared mailbox relationship, or app registration involved. - Record consent scopes, mailbox permissions, rule ownership, transport actions, and message-trace identifiers. - Distinguish client-visible symptoms from server-side mailbox or transport state. ### 2. Prove The Mailbox Effect - Correlate consent logs, sign-ins, message traces, inbox rules, transport rules, forwarding settings, and mailbox audit events. - Show which rule or token produces which concrete effect: silent forwarding, marking read, deletion, delegate access, or message rerouting. - Keep message IDs, sender or recipient pairs, and timestamps aligned across logs. ### 3. Reduce To The Decisive Abuse Chain - Compress the path to the smallest sequence: lure or grant -> token or delegate edge -> mailbox or transport mutation -> resulting mail effect. - State clearly whether persistence lives in consent, mailbox rules, transport config, or shared mailbox permissions. - If the task broadens into host pivots or Kerberos acceptance, switch back to the broader identity skill. ## Read This Reference - Load `references/mailbox-abuse.md` for the consent checklist, rule checklist, and evidence packaging. ## What To Preserve - Consent scopes, token claims, mailbox permissions, rule definitions, forwarding targets, and message IDs - Message-trace lines, audit events, and mailbox effects tied to the same mail path - The smallest replayable sequence that proves persistence, exfiltration, or delegate access
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill