competition-linux-credential-pivot

A specialized CTF workflow for tracing Linux credentials and secrets, such as SSH keys, cloud tokens, service credentials, and socket access, to the systems that accept them.

In plain words
What is it for?
It is for examining credential files, process data, environment variables, service sockets, sudo rules, setuid programs, capabilities, and proven local or host-to-host access paths.
Why use it?
It helps show whether finding a secret leads to usable access, and separates gaining more rights on one host from moving to another host.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/zhaoxuya520/reverse-skill/competition-linux-credential-pivot
Any agent
npx skills add zhaoxuya520/reverse-skill --skill competition-linux-credential-pivot
Clone the repo
git clone --depth 1 https://github.com/zhaoxuya520/reverse-skill

Made for: Claude Code, Codex.

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00110 $0.00572
Opus 5 $0.00055 $0.00286
Sonnet 5 $0.00022 $0.00114
Haiku 4.5 $0.00011 $0.00057

Measured yesterday against content hash f00c32a3361c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

competition-linux-credential-pivot scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Linux credential artifacts, service tokens, SSH material, cloud and container secrets, socket-level trust, and host-to-host pi
Origin

Copies of this mod

4 near-identical copies found in the catalogue:

CTF-Sandbox-Orchestrator/competition-linux-credential-pivot/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Competition Linux Credential Pivot

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 decisive edge is Linux credential material and where that material is accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate credential storage from accepted privilege.
  2. Record user, process, namespace, socket, key file, and service trust boundary before conclusions.
  3. Keep artifact recovery, replay path, and resulting capability in one chain.
  4. Distinguish local escalation from lateral host pivot.
  5. Reproduce one minimal artifact-to-accepted-access path.

Workflow

1. Map Credential And Trust Artifacts

  • Record SSH keys, agent sockets, kubeconfigs, cloud tokens, service-account secrets, env vars, config files, and process memory clues.
  • Note sudoers rules, capabilities, setuid binaries, systemd unit context, and namespace boundaries.
  • Keep each artifact tied to owner, scope, and expected accepting service.

2. Prove Replay And Pivot

  • Show where key, token, socket, or secret is accepted: SSH, API, Unix socket, container runtime, or control-plane endpoint.
  • Record host target, protocol, principal, and resulting session or privilege.
  • Distinguish authentication success from useful capability gain.

3. Reduce To Decisive Linux Pivot Chain

  • Compress to: recovered artifact -> accepted replay path -> pivot host or privilege transition -> resulting capability.
  • State whether root cause is weak key handling, token leakage, socket trust, sudo or capability abuse, or namespace crossover.
  • If the chain pivots into kernel exploit boundaries, hand off to kernel container escape skill.

Read This Reference

  • Load references/linux-credential-pivot.md for artifact checklists, replay matrix, and evidence packaging.

Read the full file on GitHub · 51 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 51 lines · 110 tokens per session scan B f00c32a3361c

Subscribe to this mod's changes

competition-linux-credential-pivot is a skill published in the GitHub repository zhaoxuya520/reverse-skill (31,677 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 572 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens