Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gtapps/hermitd/plugin install hermitd-laravel-forgeWrote 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/gtapps/hermitd/forge-deploy)<a href="https://agentmods.dev/skills/gtapps/hermitd/forge-deploy"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/forge-deploy/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/gtapps/hermitd/forge-deploy"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/forge-deploy.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.00069 | $0.01414 |
| Opus 5.5 | $0.00028 | $0.00566 |
| Sonnet 5.5 | $0.00014 | $0.00283 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
forge-deploy 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- forge-deploy — 88% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Deploy
Trigger a deployment on a Forge site. Always preview before deploying. A wrong deploy targets the wrong site — preview eliminates that risk.
Surface-then-approve flow
Step 1 — Preview (read-only, never mutates)
php ${CLAUDE_PLUGIN_ROOT}/php/forge.php preview-deploy <server> <site>
Resolves <server> and <site> to their canonical SDK records and prints:
--- Deploy preview (no action taken) ---
Server: prod-web-01 (ID: 12345, IP: 1.2.3.4)
Site: myapp.com (ID: 67890)
Exit 0. No network write.
Step 2 — Relay canonical target to operator
Show the canonical server name, IP, site name, and IDs.
Step 3: Deploy
php ${CLAUDE_PLUGIN_ROOT}/php/forge.php deploy <server> <site>
This triggers the deployment and returns immediately (no blocking wait):
Deployment started: deploy-id=991 server-id=12345 site-id=67890 status=queued
Watch with: forge.php deploy-watch 12345 67890 991
Capture the canonical deploy-id, server-id, and site-id — Step 4 needs them.
Step 4 — Watch via the hermit watch registry (non-blocking)
Do not poll in a foreground Bash call: a real deploy can outlast the Bash tool timeout, which would kill the wait and skip the incident. Arm a hermit watch instead: it runs detached, notifies you on each status change and on the terminal state at zero token cost while quiet, and is tracked in monitors.runtime.json (visible via /hermitd:watch status, cancellable via /hermitd:watch stop, and cleaned up when the watch finishes or is stopped).
Requires a running resident. If the resident is unavailable, run deploy-status manually.
Resolve ${CLAUDE_PLUGIN_ROOT} to its absolute path now (at skill-execution time): the variable is NOT available inside the watch subprocess. Then arm the watch by invoking /hermitd:watch with this command (substitute the absolute path and the three IDs):
php /ABS/php/forge.php deploy-watch <server-id> <site-id> <deploy-id>
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.
- 11d ago First seen · 136 lines · 69 tokens per session scan A 08bc620602f8
forge-deploy is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,414 once invoked, about $0.0003 per session on Opus 5.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-10-02.
Other skills, from other repositories
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
forge-cost
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
forge-infra
Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
forge-recon
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".
flux-recon
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".
forge-audit
Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".