zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-agent-cloud
competition-agent-cloud
VerifiedInternal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AI-agent, prompt-injection, MCP or toolchain, cloud, container, CI/CD, and supply-chain challenges. Use when the user asks to analyze prompt-to-tool flows, retrieval poisoning, mounted secrets, deployment drift, runtime-vs-manifest mismatches, registry provenance, or CI-produced artifacts under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| agents/openai.yaml | config | 379 B |
| references/agent-cloud.md | markdown | 1.1 KB |
references/agent-cloud.md
View on GitHub# Agent, Toolchain, Cloud, And Supply-Chain Checklist
## Agentic Path
- Map instruction layers, retrieval layers, memory layers, tool gates, auth material, and side effects
- Keep one compact evidence block for prompts, retrieved text, planner drift, tool arguments, and side effect
- Prove one minimal exploit chain before exploring variants
## Cloud And Container Path
- Compare checked-in manifests to live mounts, env, sidecars, and logs
- Treat metadata services, registries, message buses, object stores, and IAM-like identities as sandbox control surfaces when they appear in-path
- Track build-time, deploy-time, and runtime separately
## Supply Chain
- Keep a compact provenance chain: source -> dependency resolution -> build -> package/sign -> publish -> runtime consumer
- Focus on version drift, registry pulls, generated artifacts, and final runtime hook points
## Common Pitfalls
- Trusting a prompt string without runtime confirmation
- Treating checked-in manifests as deployment truth
- Missing the point where retrieved content becomes executable tool input
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |