Azure Pipelines Log Downloader
ansible/ansible
Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.
Provides information on how to develop Ludus configuration files
Install Ludus Development
$ npx skills add SpecterOps/skills --skill ludus-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SpecterOps/skills ludus-development --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/ludus/skills/ludus-development .claude/skills/ludus-development && 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 "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .claude/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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/ludus/skills/ludus-developmentType 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 ludus-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SpecterOps/skills ludus-development --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/ludus/skills/ludus-development .agents/skills/ludus-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .agents/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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 ludus-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SpecterOps/skills ludus-development --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/ludus/skills/ludus-development .cursor/skills/ludus-development && 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 "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .cursor/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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/ludus/skills/ludus-development--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 ludus-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SpecterOps/skills ludus-development --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/ludus/skills/ludus-development .gemini/skills/ludus-development && 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 "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .gemini/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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 ludus-developmentInstalls 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 ludus-development -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/ludus/skills/ludus-development .github/skills/ludus-development && 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 "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .github/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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 ludus-development -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 ludus-development --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/ludus/skills/ludus-development .opencode/skills/ludus-development && 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 "ludus-development" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/ludus/skills/ludus-development into .opencode/skills/ludus-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ludus-development", 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
ludus-development- GitHub stars
- 702
- Token cost
- ~1.1k tokens
- SKILL.md length
- 543 words
- Files
- 51 (incl. references, assets)
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides information on how to develop Ludus configuration files
- DevOps & Cloud work in your project
- SKILL.md covers When to Use, When NOT to Use, Terminology and Ludus Overview, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ludus Development is an agent skill from SpecterOps/skills. Provides information on how to develop Ludus configuration files
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 53 other files, including reference files and assets (for example `agents/openai.yaml`, `references/INDEX.md` and `references/admin-notes.md`).
It sits in DevOps & Cloud. It works with Ansible. The repository describes itself as: A marketplace for LLM skills. The licence is MIT.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “Use the ludus-development skill to provide information on how to develop Ludus configuration files”
- “/ludus-development”
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
No URLs in SKILL.md.
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
Ludus Development loads about 1.1k tokens when it runs, and up to ~90k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 543 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 MIT licence (© SpecterOps). 543 words, ~1,061 tokens.
Download SKILL.mdSave it as
.claude/skills/ludus-development/SKILL.md (or your agent's skills folder). This skill also uses 50 other files; get the full folder from GitHub.- name
- ludus-development
- description
- Provides information on how to develop Ludus configuration files
- license
- MIT
- metadata.author
- xpn
- metadata.version
- 0.2.0
- metadata.category
- security
Ludus Configuration Skill
When to Use
Use this skill when tasked to work on a project related to Ludus, including Ludus range configurations, Ludus roles, Ludus CLI usage, Ludus API interaction, or Ludus supporting files.
When NOT to Use
Do not use this skill when the task you are given does not mention Ludus.
Terminology
- Ludus - A system to build easy to use cyber environments ("ranges") for testing and development, built on Proxmox
- Range - A collection of VMs, networks, and firewall rules deployed by Ludus from a single YAML configuration file
- Template - A base VM image built from ISO that Ludus clones to create range VMs
- VLAN - Virtual LAN segments within a range; each VLAN becomes the third octet of the VM's IP (e.g., VLAN 10 = 10.X.10.Y)
- Testing Mode - A Ludus state that snapshots VMs and blocks internet access for safe tool/technique testing
- Router VM - A Debian-based VM automatically deployed per range that handles routing, DNS (AdGuard Home), and firewall rules
- Deploy Tags - Ansible tags that control which parts of the deployment process run (e.g.,
vm-deploy,network,user-defined-roles) - Role - An Ansible role added to Ludus and applied to VMs during deployment for additional configuration
Ludus Overview
Ludus is a system to build easy to use cyber environments, or "ranges" for testing and development.
Built on Proxmox, Ludus enables advanced automation while still allowing easy manual modifications or setup of virtual machines and networks.
Ludus is implemented as a server that runs Packer and Ansible to create templates and deploy complex cyber environments from a single configuration file. Ludus is accessed via the Ludus CLI (client) or the Proxmox web interface. Normal users should not need to access Ludus via SSH.
Users can always make manual changes or set up manual environments via Proxmox instead of/in addition to Ludus managed VMs/networks. Ludus is an automation overlay on top of Proxmox, not a 100% replacement for manual configuration - just most of the common setup tasks!
Show full SKILL.md (220 more words)Show less
Key Concepts
- Range configs are YAML files with a
ludusarray of VM definitions plus optionalnetwork,router,defaults, andnotifysections - VMs are assigned to VLANs (2-255) and given a unique
ip_last_octetwithin the VLAN - IP addresses follow the pattern:
10.<range_number>.<vlan>.<ip_last_octet> - The
{{ range_id }}template string in configs resolves to the user's ID (e.g., "JD") - Windows VMs require a
windowskey; Linux VMs requirelinux: true; macOS VMs requiremacOS: true - Ansible roles are added via
ludus ansible role addand referenced in therolesarray per VM - Network firewall rules use iptables on the router VM with
LUDUS_USER_RULESandLUDUS_DEFAULTSchains
References
For detailed information on specific areas of Ludus, consult the Reference Index which catalogs all available documentation.
Key references for common tasks:
- Reference Index - Master index of all documentation with descriptions and when to reference each document
- Range Configuration - Full annotated range config YAML example with all fields
- Range Config Schema - JSON schema reference for all config properties, types, constraints, and enum values
- API Reference - Complete REST API endpoint documentation
- CLI Reference - All Ludus CLI commands and flags
- Networking - Network architecture, VLANs, firewall rules, and packet capture
- Templates - Template management, creation, and performance tuning
- Roles - Using Ansible roles with Ludus and the community role catalog
- Deploy Tags - Controlling partial deployments with tags
- Troubleshooting - Solutions for common issues
© SpecterOps, MIT. 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 50 other files (references, assets) in plugins/ludus/skills/ludus-development of SpecterOps/skills.
- SKILL.md
- agents/openai.yaml
- assets/icon.png
- assets/icon.svg
- references/INDEX.md
- references/admin-notes.md
- references/api.md
- references/cli.md
- references/configuration.md
- references/deploy-azure.md
- references/deploy-bare-metal.md
- references/deploy-google-cloud.md
- references/deploy-hyper-v.md
- references/deploy-proxmox.md
- references/deploy-tags.md
- references/deploy-vmware-fusion.md
- references/developers.md
- references/dns.md
- … and 33 more
Open the folder on GitHubat commit e655f93
Compare with similar skills
Ludus Development 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 |
|---|---|---|---|---|---|---|
| Ludus Development this skillSpecterOps/skills | 702 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Azure Pipelines Log Downloaderansible/ansible | 71k | — | ~825 | Automated safety check: Pass | GPL-3.0 | |
| Wdio Testingansible/vscode-ansible | 487 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Spa Create Configsplunk/splunk-platform-automator | 137 | — | ~3.5k | Automated safety check: Pass | Proprietary | |
| Spa Add Test Scenariosplunk/splunk-platform-automator | 137 | — | ~2.2k | Automated safety check: Pass | Proprietary | |
| Frontend Overlayansible/ansible-ui | 113 | — | ~2.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Wdio Testing
ansible/vscode-ansible
Write, run, and debug WebDriverIO (WDIO) UI tests for the Ansible VS Code extension.
Spa Create Config
splunk/splunk-platform-automator
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
Spa Add Test Scenario
splunk/splunk-platform-automator
A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
Frontend Overlay
ansible/ansible-ui
Product-specific frontend wrappers, API clients, and paths for ansible-ui.
Chezmoi Reconcile
narze/dotfiles
Reconcile drift between the local machine and the chezmoi dotfiles repo, deciding per file whether the machine edit or the repo source wins.
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
Categories
Questions about Ludus Development
What does Ludus Development do?
Provides information on how to develop Ludus configuration files. Ludus Development is an agent skill from SpecterOps/skills.
When should I use Ludus Development?
Ludus Development fits situations like: devOps & Cloud work in your project.
How do I install Ludus Development in Claude Code?
Run `npx skills add SpecterOps/skills --skill ludus-development -a claude-code`. Or copy the skill folder (plugins/ludus/skills/ludus-development in SpecterOps/skills) into .claude/skills/ludus-development in your project. Claude Code loads it when a task matches its description.
How do I install Ludus Development in Codex?
Run `npx skills add SpecterOps/skills --skill ludus-development -a codex`. Or copy the skill folder (plugins/ludus/skills/ludus-development in SpecterOps/skills) into .agents/skills/ludus-development in your project. Codex loads it when a task matches its description.
Can I use Ludus Development 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 ludus-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ludus-development, .gemini/skills/ludus-development, .github/skills/ludus-development and .opencode/skills/ludus-development in your project.
What does Ludus Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Ludus Development is instructions for the agent only.
Does Ludus Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ludus Development 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 Ludus Development use?
Ludus Development is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ludus Development use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 89k tokens, read only when the agent opens those files.
What are the alternatives to Ludus Development?
Skills that share tags, products or a category with Ludus Development: Azure Pipelines Log Downloader (ansible/ansible, 71k stars), Wdio Testing (ansible/vscode-ansible, 487 stars), Spa Create Config (splunk/splunk-platform-automator, 137 stars) and Spa Add Test Scenario (splunk/splunk-platform-automator, 137 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ludus Development?
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.