What is maintain-wordpress?

A maintenance workflow for WordPress sites on Hostinger, the web-hosting service. It checks versions, known security problems and site health, then updates approved items and verifies that each site still loads.

Use it to review WordPress core, plugins and themes, apply approved updates, purge caches and confirm site health.

It replaces manual checks across one or many sites and helps catch outdated software or failed updates. It also reduces the risk of updating sites in the wrong order.

maintain-wordpress — Skill for Claude Code and Codex by hostinger

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.

Any agent

npx skills add hostinger/api-mcp-server --skill maintain-wordpress

Clone the repo

git clone --depth 1 https://github.com/hostinger/api-mcp-server

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hostinger/api-mcp-server/maintain-wordpress/github.svg)](https://agentmods.dev/skills/hostinger/api-mcp-server/maintain-wordpress)

Your own site

<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/maintain-wordpress"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/maintain-wordpress/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/maintain-wordpress"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/maintain-wordpress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,288 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00124	$0.01288
Opus 5.5	$0.00050	$0.00515
Sonnet 5.5	$0.00025	$0.00258
Haiku 4.5	$0.00012	$0.00129

Measured 16d ago against content hash a2d9ba37087c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maintain-wordpress scanned grade A with 1 finding 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 16d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

2. `curl -s -o /dev/null -w "%{http_code}\n" https://DOMAIN/` and the same for `https://DOMAIN/wp-login.php` — both should be `200` with no PHP error in the body.

skills/maintain-wordpress/SKILL.md · 75 lines

How it starts

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

Maintain WordPress

Check first, report, then update only what the user approves — one site at a time, proving each still loads before moving to the next.

Calling the operations

Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "wordpress plugins update").
Batch reads with multi-execute (up to 20 steps a batch). Batches chain operations from one server only — the Hostinger Connector runs wordpress, hosting and agency-hosting as separate servers.
Updates, activations, uninstalls and core changes are queued jobs: a success response means "queued". Poll the matching read operation every 10–20 s until the change shows; never re-send the write.

1. Find the installs

One site: wordpress_installations_list with domain (substring match — take the exact entry). Every site: wordpress_installations_list without filters, adding ownership: "all" to include sites the user manages for others.
Keep id (the software parameter of every wordpress_* call), username, domain, directory, is_valid and validation_error.
Agency Plan WordPress sites come from agency-hosting_websites_list-plan with website_types: ["wordpress"]. When wordpress_installations_list does not include them, only agency-hosting_wordpress_settings and core version changes (agency-hosting_wordpress_list-versions, agency-hosting_wordpress_change-version) are available; plugins and themes are updated from wp-admin.

2. Check (read-only)

Per install:

wordpress_installations_show-core-version — core version and the known vulnerabilities that affect it.
wordpress_installations_list-core-updates — available core versions.
wordpress_plugins_list-installed — status, update (the newer version, when there is one) and vulnerabilities[] with fixed_in.
wordpress_themes_list-installed — the same for themes.

Four steps per install fit five installs in one batch. For an install with is_valid: false, run wordpress_installations_check-if-are-valid with force: true for a fresh reason and leave it out of updates — a broken install is the troubleshoot-website skill's job.

Read the full file on GitHub · 75 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.

16d ago First seen · 75 lines · 124 tokens per session scan A a2d9ba37087c

Subscribe to this mod's changes

maintain-wordpress is a skill published in the GitHub repository hostinger/api-mcp-server (163 stars, last pushed yesterday), licensed MIT. It adds 124 tokens to every session and 1,288 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.

DevOps and cloud Security ai api claude cursor hostinger mcp

Contract Testing with Pact

Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.

PramodDutta/qaskills · 29 tokens

API Rate Limiting Testing

Testing API rate limiting implementations including throttling behavior, burst handling, rate limit headers, and distributed rate limiting patterns.

PramodDutta/qaskills · 29 tokens

API Fuzzing

API endpoint fuzzing for discovering unexpected behaviors, crashes, and security vulnerabilities through malformed requests, boundary values, and protocol violations.

PramodDutta/qaskills · 30 tokens

API Versioning Testing

Testing API versioning strategies including URL path, header, and query parameter versioning with backward compatibility validation.

PramodDutta/qaskills · 26 tokens

Contract-First Testing

Contract-first testing approach using Pact, Spring Cloud Contract, or Dredd for ensuring API consumer-provider compatibility.