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 cacheforge-ai/cacheforge-skills --skill log-divegit clone --depth 1 https://github.com/cacheforge-ai/cacheforge-skillsWrote 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/cacheforge-ai/cacheforge-skills/log-dive)<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/log-dive"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/log-dive/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/cacheforge-ai/cacheforge-skills/log-dive"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/log-dive.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.03052 |
| Opus 5.5 | $0.00017 | $0.01221 |
| Sonnet 5.5 | $0.00008 | $0.00610 |
| Haiku 4.5 | $0.00004 | $0.00305 |
Grade A, and why
log-dive 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.
| "curl: command not found" | curl not installed | `apt install curl` or `brew install curl` | How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Dive — Unified Log Search 🤿
Search logs across Loki, Elasticsearch/OpenSearch, and AWS CloudWatch from a single interface. Ask in plain English; the skill translates to the right query language.
⚠️ Sensitive Data Warning: Logs frequently contain PII, secrets, tokens, passwords, and other sensitive data. Never cache, store, or repeat raw log content beyond the current conversation. Treat all log output as confidential.
Activation
This skill activates when the user mentions:
- "search logs", "find in logs", "log search", "check the logs"
- "Loki", "LogQL", "logcli"
- "Elasticsearch logs", "Kibana", "OpenSearch"
- "CloudWatch logs", "AWS logs", "log groups"
- "error logs", "find errors", "what happened in [service]"
- "tail logs", "follow logs", "live logs"
- "log backends", "which log sources", "log indices", "log labels"
- Incident triage involving log analysis
- "log-dive" explicitly
Permissions
permissions:
exec: true # Required to run backend scripts
read: true # Read script files
write: false # Never writes files — logs may contain secrets
network: true # Queries remote log backends
Example Prompts
- "Find error logs from the checkout service in the last 30 minutes"
- "Search for timeout exceptions across all services"
- "What log backends do I have configured?"
- "List available log indices in Elasticsearch"
- "Show me the labels available in Loki"
- "Tail the payment-service logs"
- "Find all 5xx errors in CloudWatch for api-gateway"
- "Correlate errors between user-service and payment-service"
- "What happened in production between 2pm and 3pm today?"
Backend Configuration
Each backend uses environment variables. Users may have one, two, or all three configured.
Loki
| Variable | Required | Description |
|---|---|---|
LOKI_ADDR |
Yes | Loki server URL (e.g., http://loki.internal:3100) |
LOKI_TOKEN |
No | Bearer token for authentication |
LOKI_TENANT_ID |
No | Multi-tenant header (X-Scope-OrgID) |
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 335 lines · 42 tokens per session scan A 1b9b4f4c7af4
log-dive is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 3,052 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
open_rca_diagnosis
A structured method for finding the root cause of failures in microservices by examining measurements, request traces, and logs. It uses thresholds and cross-checks to connect symptoms to causes.
cross-source-correlation
Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which deploy caused this bug" without manual tab-switching.
design-incident-response
Use when creating or improving an incident response process for a production system or operational team.
sre-runbooks
Safe-by-default DevOps/SRE runbook automation for incident response, postmortems, on-call handovers, and operational troubleshooting. Implements Google SRE principles with agent-safe execution patterns including dry-run modes, human approval gates, and blast-radius limits.
k8s-logging-pipeline
A troubleshooting workflow for collecting logs from Kubernetes, a system for running containerised applications. It covers Fluentd and Filebeat, tools commonly used to collect and forward those logs.