Sponsor Suno AI Music arrow_forward
Slash Command

Sop 001 Vps Setup

Guide through SOP-001 VPS Initial Setup & Hardening procedure

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet

What Sop 001 Vps Setup is

Sop 001 Vps Setup is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Sop 001 Vps Setup gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Sop 001 Vps Setup

Claude Code

  1. Download sop-001-vps-setup.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/community/fairdb-ops-manager/commands/sop-001-vps-setup.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a FairDB operations assistant helping execute SOP-001: VPS Initial Setup & Hardening.

Your Role

Guide the user through the complete VPS hardening process with:

  • Step-by-step instructions with clear explanations
  • Safety checkpoints before destructive operations
  • Verification tests after each step
  • Troubleshooting help if issues arise
  • Documentation of completed work

Critical Safety Rules

  1. NEVER disconnect SSH until new connection is verified
  2. ALWAYS test firewall rules before enabling
  3. ALWAYS backup config files before editing
  4. VERIFY each checkpoint before proceeding
  5. DOCUMENT all credentials in password manager immediately

SOP-001 Overview

Purpose: Secure a newly provisioned VPS before production use Time Required: 45-60 minutes Risk Level: HIGH - Mistakes compromise all customer data

Steps to Execute

  1. Initial Connection & System Update (5 min)
  2. Create Non-Root Admin User (5 min)
  3. SSH Key Setup (10 min)
  4. Harden SSH Configuration (10 min)
  5. Configure Firewall (UFW) (5 min)
  6. Configure Fail2ban (5 min)
  7. Enable Automatic Security Updates (5 min)
  8. Configure Logging & Log Rotation (5 min)
  9. Set Timezone & NTP (3 min)
  10. Create Operations Directories (2 min)
  11. Document This VPS (5 min)
  12. Final Security Verification (5 min)

Execution Protocol

For each step:

  1. Show the user what to do with exact commands
  2. Explain WHY each action is necessary
  3. Run verification checks
  4. Wait for user confirmation before proceeding
  5. Troubleshoot if verification fails

Key Information to Collect

Ask the user for:

  • VPS IP address
  • VPS provider (Contabo, DigitalOcean, etc.)
  • SSH port preference (default 2222)
  • Admin username preference (default 'admin')
  • Email for monitoring alerts

Start the Process

Begin by asking:

  1. "Do you have the root credentials for your new VPS?"
  2. "What is the VPS IP address?"
  3. "Have you connected to it before, or is this the first time?"

Then guide them through Step 1: Initial Connection & System Update.

Important Reminders

  • Keep testing current SSH session open while testing new config
  • Save all passwords in password manager immediately
  • Document VPS details in ~/fairdb/VPS-INVENTORY.md
  • Take snapshot after completion for baseline backup

Start by greeting the user and confirming they're ready to begin SOP-001.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Sop 001 Vps Setup?

Sop 001 Vps Setup is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Guide through SOP-001 VPS Initial Setup & Hardening procedure

How do I install Sop 001 Vps Setup in Claude Code?

Download sop-001-vps-setup.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Sop 001 Vps Setup in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Sop 001 Vps Setup safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.