AGENT SKILL

competition-graphql-rpc-drift

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, generated clients, OpenAPI drift, hidden operations, and contract-to-handler mismatches. Use when the user asks to inspect GraphQL or RPC requests, compare client contracts to live handlers, recover hidden operations, trace generated clients, or explain how schema or contract drift produces the decisive behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

License 许可
MIT
最近更新
2026-10-15
Stars
★ 42
Forks
24

01 前言 Front Matter

name
competition-graphql-rpc-drift
description
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for GraphQL schemas, persisted queries, RPC manifests, generated clients, OpenAPI drift, hidden operations, and contract-to-handler mismatches. Use when the user asks to inspect GraphQL or RPC requests, compare client contracts to live handlers, recover hidden operations, trace generated clients, or explain how schema or contract drift produces the decisive behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

02 资源文件 2

03 SKILL.md 正文

Competition Graphql Rpc Drift

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 hard part is matching declared contracts with live handlers to find hidden, stale, or privileged operations.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Collect the declared contract surface first: schema, manifest, generated client, persisted query map, or OpenAPI spec.
  2. Record actual request shapes, operation names, variables, method, path, and auth context before mutating anything.
  3. Compare declared contract, generated client behavior, and live handler behavior side by side.
  4. Preserve one accepted operation and one drifted or hidden operation with the smallest delta.
  5. Reproduce the smallest contract-to-handler mismatch that proves the decisive branch.

Workflow

1. Map The Declared Contract Surface

  • Record GraphQL schema, introspection output, persisted query ids, RPC manifests, generated clients, or OpenAPI documents that define the intended surface.
  • Note versioned endpoints, client-only guards, hidden enums, optional fields, and operation naming conventions.
  • Keep document source and generation path tied to the observed requests.

2. Prove Live Handler Behavior

  • Capture the real request and response pairs, including operation name, variables, headers, cookies, and status.
  • Compare client-side validation, schema expectations, and live handler normalization or fallback behavior.
  • Record hidden operations, stale fields, undocumented methods, or handler-only branches that still execute.

3. Reduce To The Decisive Drift Path

  • Compress the result to the smallest sequence: declared contract -> actual request -> handler branch -> resulting capability.
  • State clearly whether the decisive drift lives in generated client assumptions, persisted query mapping, schema version skew, RPC manifest mismatch, or handler-side hidden logic.
  • If the task shifts into generic JWT, OAuth, or queue behavior after acceptance, hand off to the tighter specialized skill.

Read This Reference

  • Load references/graphql-rpc-drift.md for the contract checklist, live-handler checklist, and evidence packaging.

What To Preserve

  • Schemas, manifests, generated clients, persisted query ids, operation names, and version markers
  • One accepted and one drifted request pair that proves the mismatch
  • One minimal contract-to-handler sequence that reaches the decisive effect

04 同仓库更多 Skills

longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

yingan-tuoxiu

Owner-authorized YingAn/YingPo Android APK shell rehydration and stable rebuild workflow. Use for APKs with tiny or abnormal root DEX files, v.m.p or abcd655xx shell callbacks, libabcd/lib*shellservice_dex native loaders, protected assets, runtime-loaded DEX images, hidden real Application or Activity routes, and native lifecycle wrappers that must be recovered into a normally installable, signed multidex APK without changing product authentication or business authorization behavior.

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

reverse-engineering

Use when performing reverse engineering on any target: websites, desktop binaries (PE/ELF), mobile apps (APK/IPA), or network protocols. Covers web scraping/API reverse, disassembly and decompilation, Frida/Xposed hooking, il2cpp/Unity reverse, protocol capture and replay, encryption/signature analysis, and memory debugging. Triggers: 逆向、反编译、Hook、脱壳、抓包、协议分析、Frida、Xposed、il2cpp、Unity逆向、 内存扫描、DLL注入、PE分析、ELF分析、APK逆向、IPA逆向、反混淆、签名分析、加密还原、 smali、Ghidra、IDA、Cheat Engine、mitmproxy、Wireshark、脱壳、加固、SO逆向、Web逆向。

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

game-hacking

游戏辅助开发全链路助手——覆盖内存读写、协议分析、反编译、Hook 技术、驱动级隐藏、自动化脚本。 支持 C/C++、Python、x86/x64 汇编、DirectX/OpenGL。适用于 PC 端游、Android/iOS 手游、主机游戏。 当用户提到以下任何关键词时必须触发:游戏外挂、游戏辅助、内存修改、CE教程、游戏Hook、 协议分析、反编译、驱动隐藏、游戏脚本、按键精灵、游戏逆向、内存扫描、指针追踪、DLL注入、 游戏破解、脱壳、抓包分析、Frida、Xposed、il2cpp、Unity逆向、UE4逆向、DirectX Hook、 OpenGL Hook、游戏自动化、坐标识别、模板匹配、游戏安全测试。

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

supply-chain-security

暂无简介

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

reverse-engineering

Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

radare2

Use this skill whenever the user wants to analyze binaries with radare2/r2 from the command line, including reverse engineering, disassembly, function analysis, strings/import inspection, patching, binary diffing, hex inspection, or r2 scripting. Also use it when the user mentions PE/ELF/Mach-O/DEX/WASM files together with CLI analysis, `rabin2`, `rasm2`, `radiff2`, `r2pipe`, or asks for radare2 command help on Windows/Linux/macOS.

★ 42