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/claude-code-hermit/plugin install laravel-forge-hermitWrote 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/claude-code-hermit/forge-deploy)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/forge-deploy"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/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/claude-code-hermit/forge-deploy"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/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.01420 |
| Opus 5.5 | $0.00028 | $0.00568 |
| Sonnet 5.5 | $0.00014 | $0.00284 |
| Haiku 4.5 | $0.00007 | $0.00142 |
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 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.
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, 35 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 /claude-code-hermit:watch status, cancellable via /claude-code-hermit: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 /claude-code-hermit: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.
- 1mo ago Changed 7783c03772b7
- 1mo ago Changed · -4 lines · -2 tokens per session c310c9e8b87d
- 1mo ago First seen · 140 lines · 71 tokens per session scan A b01bd3c94c74
forge-deploy is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,420 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-09-03.
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".
relay-pipeline
Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".
touch-release
Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
relay-audit
Audit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".
relay-docker
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
relay-recon
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".