Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/oxi-717/ai-native-toolkit/security-hardening)<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/security-hardening"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/security-hardening/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/security-hardening"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/security-hardening.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00157 | $0.04091 |
| Opus 5 | $0.00078 | $0.02046 |
| Sonnet 5 | $0.00031 | $0.00818 |
| Haiku 4.5 | $0.00016 | $0.00409 |
Grade B, and why
security-hardening scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo sshd -T | grep -E 'port |permitrootlogin|passwordauthentication|pubkeyauthentication|maxauthtries' Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh-copy-id -i ~/.ssh/id_ed25519.pub user@server Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Hardening
Interactive security audit and hardening skill for VPS, WordPress, and Next.js.
Default language: English. Use REPORT_LANGUAGE if set. Otherwise honor an explicit language request from the user. If neither is present, provide the analysis, findings, score, and recommendations in English. Russian output is only for an explicit Russian request or REPORT_LANGUAGE=ru.
Default mode: audit and propose first. Start by assessing the current state, then present prioritized findings and recommended changes. Do not jump straight to applying hardening changes. When moving from analysis to fixes, do it step by step with pre-checks, verification, and a rollback path for each change.
RULE ZERO: DO NOT LOCK YOURSELF OUT
Preserving admin access to the server is more important than any hardening measure. Every SSH, firewall, or network change must follow this sequence:
- Pre-check — verify current state before changing anything
- Change — apply one change at a time
- Verify — confirm the change works (from a separate session if SSH/firewall)
- Rollback path — know how to undo it before you apply it
Never recommend "apply all at once" sequences for SSH/firewall/network changes. If the user doesn't have provider console or rescue mode access, tell them to set that up first.
Workflow
When triggered, act as an interactive security auditor. Don't dump everything at once — guide the user step by step.
Phase 1: Detect the Stack
Ask or detect what the user is running:
# Auto-detect
uname -a # OS
cat /etc/os-release # Distro
systemctl list-units --type=service --state=running # Services
docker ps 2>/dev/null # Containers
ss -tlnp # Listening ports
Based on what's found:
- VPS/Linux server → use the VPS checklist below + read
${CLAUDE_PLUGIN_ROOT}/skills/security-hardening/references/vps.mdfor deep detail - WordPress → read
${CLAUDE_PLUGIN_ROOT}/skills/security-hardening/references/wordpress.md - Next.js / Node.js → read
${CLAUDE_PLUGIN_ROOT}/skills/security-hardening/references/nextjs.md - General web app → read
${CLAUDE_PLUGIN_ROOT}/skills/security-hardening/references/general-web.md
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 397 lines · 157 tokens per session scan B e139754ed149
security-hardening is a skill published in the GitHub repository OXI-717/ai-native-toolkit (8 stars, last pushed 16d ago), licensed MIT. It adds 157 tokens to every session and 4,091 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
design-patterns
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
ln-75-architecture-diagram-builder
Creates current or target architecture diagrams as the primary deliverable. Not for UI design, architecture audits, or invented structure.
code-architect
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs, data flows, and a build sequence. Use this skill when the user asks for an architecture design, an implementation plan…
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
spotpatch
A development workflow for React that connects a selected page element to its JSX or TSX source code and gathers context for review.