How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

competition-stego-media - Skill

Name: competition-stego-media
Author: zhaoxuya520

Imported from zhaoxuya520/reverse-skill (CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md). Install upstream with npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media. Copyright stays with the author.

Competition Stego Media

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 challenge lives inside a media container, hidden channel, or appended payload rather than a conventional crypto blob.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

Confirm the real container type, dimensions, duration, codec, and chunk layout before guessing a hidden layer.
Check metadata, thumbnails, sidecar files, and appended trailers before deeper signal-domain work.
Rank candidate channels by evidence: alpha, palette, LSB, transform-domain residue, frame order, or container slack.
Preserve each extracted layer separately so the transform chain stays reproducible.
Stop when the hidden payload is reproduced, not merely suspected.

Workflow

1. Establish Container Truth

Inspect headers, chunk tables, EXIF or document metadata, container indexes, thumbnails, and file size anomalies.
Compare declared format against observed structure to catch polyglots, appended archives, or malformed trailers.
Record exact offsets, frame numbers, or channel boundaries that look promising.

2. Inspect Candidate Channels

Check alpha, palette order, RGB or YUV planes, LSBs, spectrogram features, document object streams, or video frame deltas.
Prefer evidence-driven attempts over brute forcing every transform.
Note whether the payload is plain bytes, another media layer, compressed data, or an encrypted blob.

3. Reconstruct The Hidden Payload Path

Keep the chain in order: container -> channel or carrier -> extraction -> decompression or decode -> final parse.
Separate extraction success from final interpretation; a channel hit is not the same as artifact recovery.
If the problem becomes primarily about cryptography after extraction, hand off to the broader crypto skill.

Read This Reference

Load references/stego-media.md for the media checklist, channel ranking guide, and evidence packaging.

What To Preserve

File structure facts: offsets, chunks, frame numbers, stream names, metadata keys, and trailer size
Intermediate extractions and the exact command or transform used to produce them
The final recovered payload and the channel that produced it

Install competition-stego-media and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zhaoxuya520-reverse-skill-competition-stego-media", "kind": "skill", "name": "competition-stego-media", "description": "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for image, audio, video, document, and container steganography. Use when the user asks to inspect metadata, alpha or palette channels, LSBs, thumbnails, appended trailers, QR fragments, transcoding artifacts, or recover a hidden payload from media without blind brute force. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.", "publisher": "zhaoxuya520", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for image, audio, video, document, and container steganography. Use when the user asks to inspect metadata, alpha or palette channels, LSBs, thumbnails, appended trailers, QR fragments, transcoding artifacts, or recover a hidden payload from media without blind brute force. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zhaoxuya520/reverse-skill", "path": "CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md", "ref": "HEAD", "url": "https://github.com/zhaoxuya520/reverse-skill/blob/HEAD/CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md", "key": "zhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md" } }, "instructions": "# Competition Stego Media\n\nUse 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.\n\nUse this skill when the challenge lives inside a media container, hidden channel, or appended payload rather than a conventional crypto blob.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Confirm the real container type, dimensions, duration, codec, and chunk layout before guessing a hidden layer.\n2. Check metadata, thumbnails, sidecar files, and appended trailers before deeper signal-domain work.\n3. Rank candidate channels by evidence: alpha, palette, LSB, transform-domain residue, frame order, or container slack.\n4. Preserve each extracted layer separately so the transform chain stays reproducible.\n5. Stop when the hidden payload is reproduced, not merely suspected.\n\n## Workflow\n\n### 1. Establish Container Truth\n\n- Inspect headers, chunk tables, EXIF or document metadata, container indexes, thumbnails, and file size anomalies.\n- Compare declared format against observed structure to catch polyglots, appended archives, or malformed trailers.\n- Record exact offsets, frame numbers, or channel boundaries that look promising.\n\n### 2. Inspect Candidate Channels\n\n- Check alpha, palette order, RGB or YUV planes, LSBs, spectrogram features, document object streams, or video frame deltas.\n- Prefer evidence-driven attempts over brute forcing every transform.\n- Note whether the payload is plain bytes, another media layer, compressed data, or an encrypted blob.\n\n### 3. Reconstruct The Hidden Payload Path\n\n- Keep the chain in order: container -> channel or carrier -> extraction -> decompression or decode -> final parse.\n- Separate extraction success from final interpretation; a channel hit is not the same as artifact recovery.\n- If the problem becomes primarily about cryptography after extraction, hand off to the broader crypto skill.\n\n## Read This Reference\n\n- Load `references/stego-media.md` for the media checklist, channel ranking guide, and evidence packaging.\n\n## What To Preserve\n\n- File structure facts: offsets, chunks, frame numbers, stream names, metadata keys, and trailer size\n- Intermediate extractions and the exact command or transform used to produce them\n- The final recovered payload and the channel that produced it", "cost": { "context_tokens": 622 } }

competition-stego-media

About

Competition Stego Media

Quick Start

Workflow

1. Establish Container Truth

2. Inspect Candidate Channels

3. Reconstruct The Hidden Payload Path

Read This Reference

What To Preserve

Install competition-stego-media and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews