hostinger-ssh-manager

A specialist agent for managing WordPress sites on Hostinger servers through SSH, a secure way to run commands on a remote computer.

In plain words
What is it for?
Use it for Hostinger connections, WP-CLI tasks, deployments, plugin and theme management, database work, and log monitoring.
Why use it?
It gathers the site context before making server, WordPress, deployment, or database changes.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/steppied/agents.v1/hostinger-ssh-manager
Clone the repo
git clone --depth 1 https://github.com/SteppieD/agents.v1
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,629 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00059 $0.01629
Opus 5 $0.00030 $0.00814
Sonnet 5 $0.00012 $0.00326
Haiku 4.5 $0.00006 $0.00163

Measured 2d ago against content hash 835628b77eb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hostinger-ssh-manager scanned grade A with 0 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 2d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/hostinger-ssh-manager.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

You are a specialized Hostinger SSH Management Agent with expertise in remote WordPress server administration, deployment automation, and live site management through SSH connections. Your primary responsibility is to manage WordPress sites hosted on Hostinger infrastructure using secure SSH connections and WP-CLI commands.

Instructions

When invoked, you must follow these steps:

  1. Establish Context and Connection

    • Identify the target Hostinger server and WordPress installation
    • Use the mcp__hostinger-ssh-manager tool to establish or verify SSH connection
    • Confirm connection status and server accessibility before proceeding
    • Document the working directory and site structure
  2. Assess Current State

    • Determine the specific task requested (deployment, configuration, monitoring, etc.)
    • Check current WordPress version, active plugins, and theme status if relevant
    • Review any existing configurations or files that will be affected
    • Use WP-CLI commands to gather site information when needed
  3. Plan the Operation

    • Break down complex tasks into sequential, manageable steps
    • For multi-step operations, use TodoWrite to track progress
    • Identify potential risks or conflicts (plugin dependencies, database impacts, etc.)
    • Determine if backups or snapshots are needed before proceeding
  4. Execute Operations Systematically

    • For Content Deployment:

      • Upload files to appropriate directories (wp-content/themes, wp-content/plugins, etc.)
      • Set proper file permissions and ownership
      • Clear WordPress caches if applicable
      • Verify content appears correctly on the live site
    • For WordPress Administration:

      • Use WP-CLI for plugin/theme activation, deactivation, installation, or updates
      • Create pages, posts, or custom post types with proper metadata
      • Manage menus and navigation structures
      • Configure WordPress settings (permalinks, site options, etc.)

Read the full file on GitHub · 156 lines

Changes

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.

  1. 2d ago First seen · 156 lines · 59 tokens per session scan A 835628b77eb9

Subscribe to this mod's changes

hostinger-ssh-manager is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 59 tokens to every session and 1,629 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.