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.
npx agentmods add skills/abdullah1854/mcpgateway/hostinger-deploynpx skills add abdullah1854/MCPGateway --skill hostinger-deploygit clone --depth 1 https://github.com/abdullah1854/MCPGatewayWrote 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/abdullah1854/mcpgateway/hostinger-deploy)<a href="https://agentmods.dev/skills/abdullah1854/mcpgateway/hostinger-deploy"><img src="https://agentmods.dev/badge/skills/abdullah1854/mcpgateway/hostinger-deploy.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01282 |
| Opus 5 | $0.00028 | $0.00641 |
| Sonnet 5 | $0.00011 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
hostinger-deploy 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 5d 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.
5. Verify via curl at server level How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hostinger Deployment Protocol
When This Skill Activates
- "Deploy to Hostinger", "publish website", "push to production"
- "Redeploy", "site not updating", "changes not showing"
- "OPcache", "CDN cache", "hPanel"
- Any deployment where target hosting is Hostinger
Anti-Hallucination Rules (NEVER violate)
| Rule | Description |
|---|---|
| NO SSH FILE CREATION | Files created via SSH are INVISIBLE to the web server due to OPcache. Always use hPanel Git mechanism |
| CDN DISTRUST | NEVER verify deployment via browser or live URL alone. CDN caches aggressively. Verify at server level first |
| GIT-FIRST | All file changes MUST go through Git → hPanel Git deploy. Direct file uploads are unreliable |
| OPCACHE LAG | After deployment, wait for OPcache to clear before declaring success. Expect 30-60s lag minimum |
| ASK BEFORE DEPLOYING | NEVER deploy without explicit user consent |
Deployment Types
Static Sites (HTML/CSS/JS)
Tool: hostinger_hosting_deployStaticWebsite
1. Build locally (npm run build / equivalent)
2. Verify build output exists and is correct
3. Deploy via Hostinger MCP tool
4. Wait 60s for OPcache
5. Verify via curl at server level
JavaScript Apps (Next.js, React)
Tool: hostinger_hosting_deployJsApplication
1. Build locally, verify no errors
2. Check package.json has correct start script
3. Deploy via Hostinger MCP tool
4. Wait 60s for OPcache
5. Verify via curl at server level
WordPress
Tools: hostinger_hosting_deployWordpressTheme or hostinger_hosting_importWordpressWebsite
1. Build/compile theme assets
2. Deploy theme via Hostinger MCP tool
3. Clear WordPress cache (if applicable)
4. Wait 60s for OPcache
5. Verify via curl at server level
Standard Workflow
Phase 1: Pre-Deploy Checks
# 1. Verify build succeeds
npm run build # or equivalent
# 2. Run tests if available
npm test || echo "No tests configured"
# 3. Check no secrets in code
grep -r "sk_live\|api_key\|password\|secret" --include="*.ts" --include="*.js" --include="*.env" || echo "Clean"
# 4. Verify correct branch
git status
git log --oneline -3
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.
- 5d ago First seen · 141 lines · 55 tokens per session scan A a6db971ed2ab
hostinger-deploy is a skill published in the GitHub repository abdullah1854/MCPGateway (15 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,282 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
discovery-patterns
Configure ServiceNow Discovery — schedules, IP ranges, credential affinities, MID Server assignment, custom probes/sensors, identification rules, and run-status monitoring on discovery tables.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
deploy-windows
Use this skill when installing, deploying, launching, serving, or troubleshooting mesh-llm on a Windows machine — PowerShell install via install.ps1, flavor selection (CUDA/ROCm/Vulkan/CPU), source builds, the contrib helper scripts, and verifying it serves.
lambda-labs
On-demand GPU cloud instances for ML training.
aws
AWS cloud services expert for EC2, S3, Lambda, IAM, and AWS CLI.