Server Audit logo

Server Audit

Community
Firstp1ck
server-audit

Agents should invoke this skill for Linux server security reviews, SSH hardening, firewall/open-port audits, user/permission checks, exposed services, or host hardening requests. Produces severity-rated findings and practical remediation steps.

Overview

PublisherFirstp1ck
Repositorypi-coding-agent-forge
Skill nameserver-audit
Stars
93
Forks
22
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Firstp1ck on GitHub. Read the source before you install it.

Installation

Install the Server Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-server-audit/skills/server-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forge.git /tmp/pi-coding-agent-forge
mkdir -p .claude/skills
cp -r /tmp/pi-coding-agent-forge/pi-skill-server-audit/skills/server-audit .claude/skills/server-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Server Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Server Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Server Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Server Audit

Security auditing and hardening for Linux systems. Covers SSH, firewalls, ports, users, and general hardening.

Quick Start

Run a Quick Security Audit

Check the essentials in order:

bash
# 1. Open ports
ss -tlnp

# 2. SSH config
grep -E "^(PasswordAuthentication|PermitRootLogin|PubkeyAuthentication)" /etc/ssh/sshd_config

# 3. Firewall status
sudo ufw status verbose   # Ubuntu/Debian
sudo firewall-cmd --list-all  # RHEL/Arch (firewalld)
sudo iptables -L -n        # Raw iptables

# 4. Failed login attempts (last 24h)
journalctl -u sshd --since "24 hours ago" | grep -c "Failed password"

# 5. Users with login shells
grep -v "nologin\|false" /etc/passwd | cut -d: -f1

SSH Hardening

Audit Checklist

CheckCommandExpectedSeverity
Root login disabledgrep PermitRootLogin /etc/ssh/sshd_confignoCritical
Password auth disabledgrep PasswordAuthentication /etc/ssh/sshd_confignoHigh
Key auth enabledgrep PubkeyAuthentication /etc/ssh/sshd_configyesHigh
Non-standard portgrep "^Port" /etc/ssh/sshd_configNot 22 (optional)Medium
Max auth triesgrep MaxAuthTries /etc/ssh/sshd_config3 or lessMedium
Idle timeoutgrep ClientAliveInterval /etc/ssh/sshd_configSet (e.g., 300)Low
Protocol 2 onlygrep Protocol /etc/ssh/sshd_config2 (default in modern)Low
Allowed users setgrep AllowUsers /etc/ssh/sshd_configSpecific users listedMedium

Recommended SSH Config

# /etc/ssh/sshd_config — hardened
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
MaxAuthTries 3
ClientAliveInterval 300
ClientAliveCountMax 2
X11Forwarding no
AllowTcpForwarding no

After SSH Changes

bash
# Validate config before restarting
sudo sshd -t

# Restart SSH
sudo systemctl restart sshd

Firewall Audit

UFW (Ubuntu/Debian)

bash
# Status
sudo ufw status verbose

# List rules with numbers
sudo ufw status numbered

# Check default policies
sudo ufw show raw | head -20

Expected defaults:

  • Incoming: DENY
  • Outgoing: ALLOW
  • Only required ports open (22/SSH, 80/443 if web server, etc.)

Firewalld (Arch/RHEL)

bash
# Active zone and rules
sudo firewall-cmd --list-all

# List all zones
sudo firewall-cmd --get-active-zones

# Check specific port
sudo firewall-cmd --query-port=8080/tcp

Iptables (Raw)

bash
# List all rules
sudo iptables -L -n -v

# Check for wide-open rules
sudo iptables -L -n | grep "0.0.0.0/0.*ACCEPT"

Open Port Audit

Discover Listening Ports

bash
# All listening TCP ports with process names
ss -tlnp

# All listening UDP ports
ss -ulnp

# Combined with process info (requires root for all)
sudo ss -tlnp

Evaluate Open Ports

PortServiceShould Be Open?Notes
22SSHYes (if needed)Consider non-standard port
53DNS (Pi-hole)Yes (local only)Should not face internet
80/443HTTP/HTTPSDependsOnly if serving web content
3000GiteaYes (local only)Should not face internet
9222NAS SSHYes (local only)Non-standard port, good
11434OllamaYes (local only)AI inference endpoint

Scan from External Perspective

bash
# Scan a host from this machine
nmap -sT -O <target-ip>

# Quick scan common ports
nmap -F <target-ip>

# Scan specific port range
nmap -p 1-1024 <target-ip>

User and Permission Audit

Check Users

bash
# Users with login shells (potential interactive users)
grep -v "nologin\|false" /etc/passwd | cut -d: -f1

# Users with UID 0 (root-level)
awk -F: '$3 == 0 {print $1}' /etc/passwd

# Users in sudo group
getent group sudo | cut -d: -f4
getent group wheel | cut -d: -f4  # Arch/RHEL

Check Permissions

bash
# World-writable files (security risk)
find / -type f -perm -o+w 2>/dev/null | head -20

# SUID binaries (potential privilege escalation)
find / -type f -perm -4000 2>/dev/null

# Check home directory permissions
ls -la /home/

Check Sudoers

bash
# View sudoers (never edit directly, use visudo)
sudo cat /etc/sudoers
sudo ls -la /etc/sudoers.d/

Fail2ban Integration

Check Status

bash
# Fail2ban status
sudo fail2ban-client status

# SSH jail specifically
sudo fail2ban-client status sshd

# Banned IPs
sudo fail2ban-client get sshd banip --with-time

Recommended Jail Config

ini
# /etc/fail2ban/jail.local
[sshd]
enabled = true
port = ssh
filter = sshd
logpath = /var/log/auth.log
maxretry = 5
bantime = 3600
findtime = 600

Severity Ratings

When reporting audit findings, rate each item:

SeverityMeaningAction
CriticalActively exploitable, immediate riskFix now
HighSignificant risk, should fix soonFix within 24h
MediumModerate risk, best practice violationFix within a week
LowMinor improvement, defense-in-depthFix when convenient
InfoObservation, no action neededDocument only

Audit Report Format

When delivering an audit, structure it as:

  1. Executive Summary — Overall health rating, critical findings count
  2. Critical Findings — Items that need immediate attention
  3. Recommendations — Prioritized list with severity, fix commands, and reasoning
  4. What's Good — Positive findings (acknowledge what's already well-configured)

Kai skill — Security auditing and server hardening

Frequently asked questions

What does the Server Audit AI skill do?

Agents should invoke this skill for Linux server security reviews, SSH hardening, firewall/open-port audits, user/permission checks, exposed services, or host hardening requests. Produces severity-rated findings and practical remediation steps.

Why use Server Audit on TypingMind?

Because you install it once and use it with any model. Server Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Server Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-server-audit/skills/server-audit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Server Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Server Audit?

As many as you like. As long as a model supports skills, you can use Server Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Server Audit AI skill free?

Yes. It is published on GitHub by Firstp1ck under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇