Security hardening skill for AI agents that audit and improve VPS, WordPress, and Next.js security without jumping straight into risky changes.
The skill is built around one rule: do not lock yourself out of the server. It works in audit-first mode, gives findings in priority order, and produces a final 0-10 security score with an explanation in Russian by default.
SKILL.md: the main skill instructionsreferences/vps.md: deep VPS and Linux hardening referencereferences/wordpress.md: WordPress-specific hardening guidancereferences/nextjs.md: Next.js and Node.js security guidancereferences/general-web.md: general web security guidance
- Default language is Russian unless the user clearly prefers another language
- Default mode is analysis first, changes second
- Every risky change must follow
pre-check -> change -> verify -> rollback - VPS hardening includes anti-lockout workflow and break-glass recovery guidance
- Final audit includes a
0-10score plus a short explanation of why that score was given
For a VPS, the skill looks at areas such as:
- SSH posture
- Firewall and exposed services
- Recovery path and console access
- Fail2ban / CrowdSec / monitoring
- Patch management and reboot policy
- Docker exposure
- Sysctl / CIS-style hardening
- Backups, snapshots, and rollback readiness
The expected audit result is:
Итоговая оценка: X/10Краткий выводКритичные проблемыЧто уже хорошоСледующие шаги по приоритету
This repository is published primarily as a reference distribution of the skill.
- You can read it, fork it, and adapt it for your own workflows
- You should review all commands before applying them to a real server
- You should not assume every hardening recommendation is safe for every workload
Copy the skill into your agent skills directory, for example:
mkdir -p ~/.agents/skills/security-hardening
cp SKILL.md ~/.agents/skills/security-hardening/
cp -r references ~/.agents/skills/security-hardening/Then re-index your local skills if your environment requires it.
- This skill is not a substitute for testing
- Never apply SSH, firewall, or sysctl changes in bulk
- Always keep a second session and a provider recovery path available
- Always verify effective state, not just config files
This repository is published as a read-mostly reference. Outside contributions are generally not accepted directly. Please do not open drive-by pull requests. If you believe there is a serious mistake, open a tightly scoped issue with concrete evidence and reproduction details.