Skip to content
SkillModel-led552 tokens in use

competition-cloud-metadata-path

A downstream CTF-sandbox skill for cloud metadata services: it traces how instance or workload identity becomes a credential and which downstream API accepts it.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-cloud-metadata-path

Skill label

measured from its files

What installing competition-cloud-metadata-path costs

118tokens idle
552tokens in use
799tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges where the decisive edge is proving how metadata-derived identity becomes accepted privilege. The agent identifies the active metadata surface, records the reachability path, and separates three claims: metadata is reachable, a credential was issued, and a downstream API accepted it.

The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: map metadata reachability, prove credential or identity issuance, reduce to the decisive trust path
  • A reference checklist for reachability, token claims and the accepting API
  • An evidence list covering endpoints, headers, role names, audiences, issuers and privilege-bearing actions
  • Hand-off rules to the SSRF pivot skill and to the Kubernetes control-plane skill

Common Use Cases

  • Documenting how a pod or instance in a lab obtains a token from its metadata service
  • Explaining which role or audience a metadata-derived credential carries
  • Writing up the chain from a reaching surface to an accepted cloud action in a CTF

What Makes It Unique

It treats reaching the metadata service as only the first link and requires proof of issuance and acceptance. Its checklist warns about two gaps: showing metadata access without a useful credential, and mixing node identity with workload identity without showing which one drove the privilege edge.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method involves calling metadata endpoints and cloud or cluster APIs from within the sandbox, so the agent’s own shell and network tools do that work under the assumptions the orchestrator set up. The skill itself does not fetch pages, call APIs or write files.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers