logdump

A saved command workflow for taking a log from the Windows clipboard, storing it in a temporary file, and reducing it with filters. A clipboard is the temporary place where copied text is held.

In plain words
What is it for?
Starting with the latest log lines, then narrowing debugging by error level, component, text pattern, time range, or nearby context.
Why use it?
It provides a repeatable way to inspect a large log without first exposing the entire file or manually searching through it.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/launch-it-labs/log-reducer/logdump
Clone the repo
git clone --depth 1 https://github.com/launch-it-labs/log-reducer

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 455 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00455
Opus 5 $0.00000 $0.00228
Sonnet 5 $0.00000 $0.00091
Haiku 4.5 $0.00000 $0.00046

Measured yesterday against content hash e29f09c40b44, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

logdump 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 yesterday.

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.

.claude/commands/logdump.md · 41 lines

What it actually says

The user has a log on their clipboard. Dump it to a temp file and reduce it using the filters most relevant to your current debugging context.

Step 1 — Save clipboard to file (do NOT read the file contents):

powershell -command "Get-Clipboard | Set-Content C:\tmp\log.txt"

Step 2 — Call reduce_log with the filters YOU need right now:

reduce_log({ file: "C:\\tmp\\log.txt", tail: 2000 })

Start with just tail — no filters. If the output is small enough, you get it directly. If it's large, you automatically get an enhanced summary listing unique errors, warnings, timestamps, and components. Use that summary to plan your next call.

Step 3 — Drill down based on what you see:

After the initial call, narrow with the filters that match your investigation:

  • Debugging an error? Use level: "error" or level: "warning"
  • Looking at a specific component? Use component: "name"
  • Searching for a pattern? Use grep: "pattern"
  • Narrow time window? Use time_range: "HH:MM-HH:MM"
  • Need more context around matches? Use before: 30 or after: 10
  • Context window too noisy? Add context_level: "warning" to filter low-severity context lines

Example follow-up calls:

reduce_log({ file: "C:\\tmp\\log.txt", tail: 2000, level: "error", limit: 5 })
reduce_log({ file: "C:\\tmp\\log.txt", tail: 2000, time_range: "14:02-14:03", before: 50 })
reduce_log({ file: "C:\\tmp\\log.txt", tail: 2000, level: "error", before: 30, context_level: "warning" })

The raw log must NEVER enter the conversation. Do not read C:\tmp\log.txt with the Read tool. Only the reduce_log output should appear in this conversation.

Show the reduced output to the user.

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.

  1. yesterday First seen · 41 lines · 0 tokens per session scan A e29f09c40b44

Subscribe to this mod's changes

logdump is a command published in the GitHub repository launch-it-labs/log-reducer (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 455 tokens. 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-08-31.