Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-graphql-rpc-driftAPIs, SaaS and identity

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 contr⁩

v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-graphql-rpc-drift

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
9PLU3PAgw4…ZQTU4bCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package19adb1de…82c95c33
19adb1dede1f…2af682c95c333 files · ⁦1.9 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-graphql-rpc-drift@cab634b

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

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634b19adb1deSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login