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 skills add Ghosteken/agent-harness --skill appdeploygit clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/appdeploy)<a href="https://agentmods.dev/skills/ghosteken/agent-harness/appdeploy"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/appdeploy/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/ghosteken/agent-harness/appdeploy"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/appdeploy.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.00042 | $0.02285 |
| Opus 5.5 | $0.00017 | $0.00914 |
| Sonnet 5.5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
appdeploy 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 1mo 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.
description: "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl." This is a copy
100% identical to appdeploy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AppDeploy Skill
Deploy web apps to AppDeploy via HTTP API.
When to Use This Skill
- Use when planning or building apps and web apps
- Use when deploying an app to a public URL
- Use when publishing a website or web app
- Use when the user says "deploy this", "make this live", or "give me a URL"
- Use when updating an already-deployed app
Setup (First Time Only)
-
Check for existing API key:
- Look for a
.appdeployfile in the project root - If it exists and contains a valid
api_key, skip to Usage
- Look for a
-
If no API key exists, register and get one:
curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \ -H "Content-Type: application/json" \ -d '{"client_name": "claude-code"}'Response:
{ "api_key": "ak_...", "user_id": "agent-claude-code-a1b2c3d4", "created_at": 1234567890, "message": "Save this key securely - it cannot be retrieved later" } -
Save credentials to
.appdeploy:{ "api_key": "ak_...", "endpoint": "https://api-v2.appdeploy.ai/mcp" }Add
.appdeployto.gitignoreif not already present.
Usage
Make JSON-RPC calls to the MCP endpoint:
curl -X POST {endpoint} \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer {api_key}" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "{tool_name}",
"arguments": { ... }
}
}'
Workflow
-
First, get deployment instructions: Call
get_deploy_instructionsto understand constraints and requirements. -
Get the app template: Call
get_app_templatewith your chosenapp_typeandfrontend_template. -
Deploy the app: Call
deploy_appwith your app files. For new apps, setapp_idtonull. -
Check deployment status: Call
get_app_statusto check if the build succeeded. -
View/manage your apps: Use
get_appsto list your deployed apps.
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.
- 1mo ago First seen · 211 lines · 42 tokens per session scan A 05efdb1872e8
appdeploy is a skill published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,285 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to appdeploy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
software-design-system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed…
sandy-cli
Run TypeScript scripts in sandboxed microVMs or Docker containers with AWS SDK access via IMDS, through the sandy CLI. Use when investigating AWS resources, running read-only queries, or executing TypeScript automation that needs AWS credentials via shell commands.
aws-architecture
AWS architecture decisions, serverless patterns, event-driven design, service boundaries and Well-Architected Framework. Use when designing system architecture or making infrastructure tradeoffs.
aws-api
AWS API design, implementation and integration patterns. Use when creating or modifying API Gateway endpoints, OpenAPI contracts, authentication, error handling or event integrations.
distributed-consensus
Distributed consensus algorithms and logical time for cloud and multi-node systems. Covers Lamport clocks, vector clocks, FLP impossibility, Paxos (basic, multi, fast), Raft, Viewstamped Replication, Byzantine fault tolerance basics, quorum reads/writes (N/R/W), leader election, and TLA+ specification style. Use when…