Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
A skill your agent uses when the user asks about Linux process injection, using ptrace for injection, LDPRELOAD injection, writing to procfs, remote access via processvmwritev, seccomp notify…
Apache-2.0Auto-check passed
Install Linux Process Injection
$ npx skills add SpecterOps/skills --skill linux-process-injection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SpecterOps/skills linux-process-injection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .claude/skills/linux-process-injection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .claude/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SpecterOps/skills --skill linux-process-injection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SpecterOps/skills linux-process-injection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .agents/skills/linux-process-injection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .agents/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpecterOps/skills --skill linux-process-injection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SpecterOps/skills linux-process-injection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .cursor/skills/linux-process-injection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .cursor/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SpecterOps/skills.git --path plugins/tradecraft-linux/skills/linux-process-injection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SpecterOps/skills --skill linux-process-injection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SpecterOps/skills linux-process-injection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .gemini/skills/linux-process-injection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .gemini/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SpecterOps/skills linux-process-injectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SpecterOps/skills --skill linux-process-injection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .github/skills/linux-process-injection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .github/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpecterOps/skills --skill linux-process-injection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SpecterOps/skills linux-process-injection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/tradecraft-linux/skills/linux-process-injection .opencode/skills/linux-process-injection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linux-process-injection" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/tradecraft-linux/skills/linux-process-injection into .opencode/skills/linux-process-injection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-process-injection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linux-process-injection- GitHub stars
- 702
- Token cost
- ~706 tokens
- SKILL.md length
- 258 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user asks about Linux process injection, using ptrace for injection, LDPRELOAD injection, writing to procfs, remote access via processvmwritev, seccomp notify…
- Works in 4 steps: Classify the lifecycle. Decide whether… → Profile the target. Identify… → Validate prerequisites. Check ptrace and… → …
- The user asks about Linux process injection
- SKILL.md covers Overview, Workflow, Method Rules and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Linux Process Injection is an agent skill from SpecterOps/skills. Use this skill when the user asks about Linux process injection, using ptrace for injection, LDPRELOAD injection, writing to procfs, remote access via processvmwritev, seccomp notify injection, PTRACEPOKETEXT, GOT overwrite, remote thread creation on Linux, or bypassing Yama ptrace restrictions.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml` and `references/capability-matrix.md`).
It works with Linux. The repository describes itself as: A marketplace for LLM skills. The licence is Apache-2.0.
When your agent uses it
- The user asks about Linux process injection
- Using ptrace for injection
- LDPRELOAD injection
- Writing to procfs
Example prompts
- “/linux-process-injection”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Classify the lifecycle. Decide whether the target is already running or launched under injector control.
- Profile the target. Identify architecture, ABI, mappings, RELRO, thread state, loader/libc, kernel features, and mitigations.
- Validate prerequisites. Check ptrace and LSM/Yama policy, loader behavior, or parent-child seccomp support as applicable.
- Separate staging from execution. Identify both where bytes or objects are placed and how control reaches them.
What it can do on your machine
Read from SKILL.md and the folder at commit e655f93. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comakamai.comoutflank.nl
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linux Process Injection loads about 706 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 258 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SpecterOps/skills at commit e655f93, republished under its Apache-2.0 licence (© SpecterOps). 258 words, ~706 tokens.
Download SKILL.mdSave it as
.claude/skills/linux-process-injection/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- linux-process-injection
- description
- Use this skill when the user asks about Linux process injection, using ptrace for injection, LD_PRELOAD injection, writing to procfs, remote access via process_vm_writev, seccomp notify injection, PTRACE_POKETEXT, GOT overwrite, remote thread creation on Linux, or bypassing Yama ptrace restrictions.
- metadata.author
- Outflank
Linux Process Injection
Overview
Linux has no direct equivalents of Windows APIs like VirtualAllocEx, VirtualProtectEx, or CreateRemoteThread. Allocation, permission changes, and thread creation must be induced inside the target process rather than performed remotely. All live-process injection methods are gated by the ptrace access-check algorithm, which evaluates credentials, dumpability, capabilities, and LSM policy.
There are two primary injection models:
- Live process: modify an existing image with
ptrace,/proc/<pid>/mem, orprocess_vm_writev. Use the modeloverwrite -> execute -> recover. - Controlled launch or exec: arrange loading into a new image with
LD_PRELOADor seccomp user notification.
Consult the capability matrix for feasibility checks.
Workflow
- Classify the lifecycle. Decide whether the target is already running or launched under injector control.
- Profile the target. Identify architecture, ABI, mappings, RELRO, thread state, loader/libc, kernel features, and mitigations.
- Validate prerequisites. Check ptrace and LSM/Yama policy, loader behavior, or parent-child seccomp support as applicable.
- Separate staging from execution. Identify both where bytes or objects are placed and how control reaches them.
Method Rules
- Use
ptracefor register control, thread stops, or the broadest live-process control. - Treat
/proc/<pid>/memwrites through non-writable mappings as kernel-policy dependent. - Use
process_vm_writevonly for writable memory. - Treat
LD_PRELOADas controlled dynamic-loader behavior; static binaries, secure-execution mode, and environment sanitization can block it. - Treat seccomp notification as syscall mediation, not remote memory or register control. The seccomp-notify PoC installs a listener before
execveand substitutes a staged shared-object FD for a selected loaderopenatcall.
References
© SpecterOps, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references, assets) in plugins/tradecraft-linux/skills/linux-process-injection of SpecterOps/skills.
- SKILL.md
- agents/openai.yaml
- assets/icon.png
- assets/icon.svg
- references/capability-matrix.md
Open the folder on GitHubat commit e655f93
Compare with similar skills
Linux Process Injection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linux Process Injection this skillSpecterOps/skills | 702 | — | ~706 | Automated safety check: Pass | Apache-2.0 | |
| Configuring Horizoncoollabsio/coolify | 63k | 4 repos | ~898 | Automated safety check: Pass | MIT | |
| Engine Whats Newflutter/flutter | 179k | — | ~978 | Automated safety check: Pass | BSD-3-Clause | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Upgrade Browserflutter/flutter | 179k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| K8s Security PoliciesCybereason-Public/owLSM | 280 | 12 repos | ~2k | Automated safety check: Pass | GPL-2.0 |
Similar skills
Engine Whats New
flutter/flutter
Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Upgrade Browser
flutter/flutter
Upgrade browser versions (Chrome or Firefox) in the Flutter Web Engine and/or Framework tests.
K8s Security Policies
Cybereason-Public/owLSM
Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.
Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
More from SpecterOps/skills
All 38 skills in this repoCodex Activity Report
SpecterOps/skills
Generate a normalized UTC timeline and evidence-based narrative from Codex activity artifacts.
Com Proxy Triage
SpecterOps/skills
A skill your agent uses when the user wants to triage Windows COM proxy/hijack candidates by capturing HKCU\Software\Classes\CLSID\{...}\InProcServer32 NAME NOT FOUND lookups for a process, mapping…
Cwe Code Review
SpecterOps/skills
Perform CWE-grounded security code reviews and precise weakness mapping using a locally derived MITRE CWE corpus, relationship graphs, mapping notes, detection methods, mitigations, and schema…
Ghostwriter Oplog
SpecterOps/skills
A skill your agent uses for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.
Nmap Parse
SpecterOps/skills
Parse nmap scan output and generate actionable recon notes. An agent skill from SpecterOps/skills.
Osint Recon
SpecterOps/skills
Perform OSINT and external reconnaissance for approved targets.
Related
Works with
Questions about Linux Process Injection
What does Linux Process Injection do?
A skill your agent uses when the user asks about Linux process injection, using ptrace for injection, LDPRELOAD injection, writing to procfs, remote access via processvmwritev, seccomp notify…. Linux Process Injection is an agent skill from SpecterOps/skills. Use this skill when the user asks about Linux process injection, using ptrace for injection, LDPRELOAD injection, writing to procfs, remote access via processvmwritev, seccomp notify injection, PTRACEPOKETEXT, GOT overwrite, remote thread creation on Linux, or bypassing Yama ptrace restrictions.
When should I use Linux Process Injection?
Linux Process Injection fits situations like: the user asks about Linux process injection; using ptrace for injection; LDPRELOAD injection; writing to procfs.
How do I install Linux Process Injection in Claude Code?
Run `npx skills add SpecterOps/skills --skill linux-process-injection -a claude-code`. Or copy the skill folder (plugins/tradecraft-linux/skills/linux-process-injection in SpecterOps/skills) into .claude/skills/linux-process-injection in your project. Claude Code loads it when a task matches its description.
How do I install Linux Process Injection in Codex?
Run `npx skills add SpecterOps/skills --skill linux-process-injection -a codex`. Or copy the skill folder (plugins/tradecraft-linux/skills/linux-process-injection in SpecterOps/skills) into .agents/skills/linux-process-injection in your project. Codex loads it when a task matches its description.
Can I use Linux Process Injection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpecterOps/skills --skill linux-process-injection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linux-process-injection, .gemini/skills/linux-process-injection, .github/skills/linux-process-injection and .opencode/skills/linux-process-injection in your project.
What does Linux Process Injection need to run?
SKILL.md names no scripts, command-line tools or credentials: Linux Process Injection is instructions for the agent only.
Does Linux Process Injection access the network?
SKILL.md names 3 domains. As links in the text: github.com, akamai.com and outflank.nl. This is read from the text; nothing was executed.
Is Linux Process Injection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linux Process Injection use?
Linux Process Injection is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linux Process Injection use?
About 706 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Linux Process Injection?
Skills that share tags, products or a category with Linux Process Injection: Configuring Horizon (coollabsio/coolify, 63k stars), Engine Whats New (flutter/flutter, 179k stars), Openclaw Live Updater (openclaw/openclaw, 392k stars) and Upgrade Browser (flutter/flutter, 179k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linux Process Injection?
SpecterOps (a GitHub organization) maintains it in SpecterOps/skills, which has 702 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on September 23, 2026.
Source: SpecterOps/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.