A Laravel Forge log-reading tool for deployment, server, site, application, web-server, and background-process logs. Logs are timestamped records used to investigate what an application or server did.

Use it to read recent or specific deployment logs, inspect server and site logs, or bundle logs with deployment history for incident triage.

It gathers the records needed to investigate failed deployments and operational problems without searching through Forge manually.

forge-logs — Skill for Claude Code by gtapps/claude-code-hermit

Install

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.

Claude Code

/plugin marketplace add gtapps/claude-code-hermit

Claude Code

/plugin install laravel-forge-hermit

Made for: Claude Code.

Or install laravel-forge-hermit, the plugin that ships this one along with the rest of its 5 skills.

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/gtapps/claude-code-hermit/forge-logs/github.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/forge-logs)

Your own site

<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/forge-logs"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/forge-logs/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/gtapps/claude-code-hermit/forge-logs"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/forge-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. 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.00079	$0.00955
Opus 5.5	$0.00032	$0.00382
Sonnet 5.5	$0.00016	$0.00191
Haiku 4.5	$0.00008	$0.00096

Measured 1mo ago against content hash 3fc226ced679, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

forge-logs 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

forge-logs — 100% identical, 6 lines differ

plugins/laravel-forge-hermit/skills/forge-logs/SKILL.md · 84 lines

How it starts

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

Forge Logs

Read deployment and server logs from Forge.

Latest deployment log for a site

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php logs <server> <site>

Fetches the most recent deployment and returns its full log.

Specific deployment log

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php deploy-log <server> <site> <deploy-id>

Use deploy-history first to find the deployment ID.

Server log

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php server-log <server> <key>

Common keys: php, mysql, cron, daemon, nginx-error, nginx-access. Nginx keys are hyphenated; nginx_error (underscored) returns a 404. The PHP-FPM log key is dot-version notation matching the server's installed PHP (php-8.3, not php) — passing the literal php key auto-resolves it against the server's php_version. mysql/cron/daemon may 404 outright on servers with a custom, non-Forge-provisioned install of that service (no Forge-tracked log path) — a 404 there isn't necessarily a wrong key. Key list depends on the server's installed services.

Site logs

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php site-log <server> <site> <type>

<type> is one of application (the Laravel app log), nginx-access, nginx-error. Application and access logs leak PII and tokens more readily than deploy logs — the Secret hygiene rules below apply with extra force.

Background process log

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php background-process-log <server> <process-id>

The log path for apps that run as a Forge Background Process instead of PHP-FPM (Node apps, queue workers, custom daemons). server-log does not cover these. Find the process ID first:

echo '[<server-id>]' | php ${CLAUDE_PLUGIN_ROOT}/php/forge.php call backgroundProcesses

Triage mode

When the operator says something like "what's wrong with myapp.com" or "triage the failing site", bundle context automatically:

php ${CLAUDE_PLUGIN_ROOT}/php/forge.php site <server> <site> — confirm the site is reachable and check status fields.
php ${CLAUDE_PLUGIN_ROOT}/php/forge.php deploy-history <server> <site> — surface the last few deployments and their statuses.
php ${CLAUDE_PLUGIN_ROOT}/php/forge.php logs <server> <site> — fetch the latest deployment log.
Synthesize: identify the failure type (build error, composer error, migration error, timeout), highlight the relevant log section, and suggest a remedy.

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

1mo ago First seen · 84 lines · 79 tokens per session scan A 3fc226ced679

Subscribe to this mod's changes

forge-logs is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 955 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.

Claude Code Cloud Debugging DevOps and cloud ai ai-agent anthropic claude claude-code-plugin

forge-diagnose

Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".

tonone-ai/tonone · 63 tokens

forge-logs