clean-journal

clean-journal is a command for Claude Code from cwf818/creditgauge. It costs 18 tokens per session (286 once invoked), scanned A, original, MIT.

A cleanup command for old JSONL journal files, which are line-by-line text logs, created by CreditGauge under its runtime state folders.

In plain words
What is it for?
Use it to preview or remove journal files older than a chosen number of days, or remove all matching journals.
Why use it?
It limits disk usage from accumulated token-sample history while protecting diagnostics, cache, and main state files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the creditgauge plugin — 7 commands shipped together

Good fit Use it to preview or remove journal files older than a chosen number of days, or remove all matching journals.

Compare 6 commands from other repositories ↓
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 cwf818/creditgauge
Claude Code
/plugin install creditgauge

Made for: Claude Code.

Or install creditgauge, the plugin that ships this one along with the rest of its 7 commands.

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.

agentmods badge for clean-journal

README.md
[![agentmods](https://agentmods.dev/badge/commands/cwf818/creditgauge/clean-journal/github.svg)](https://agentmods.dev/commands/cwf818/creditgauge/clean-journal)
Your own site
<a href="https://agentmods.dev/commands/cwf818/creditgauge/clean-journal"><img src="https://agentmods.dev/badge/commands/cwf818/creditgauge/clean-journal/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.

agentmods 80×15 button for clean-journal

Your own site · 80×15
<a href="https://agentmods.dev/commands/cwf818/creditgauge/clean-journal"><img src="https://agentmods.dev/badge/commands/cwf818/creditgauge/clean-journal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 286 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00286
Opus 5 $0.00009 $0.00143
Sonnet 5 $0.00004 $0.00057
Haiku 4.5 $0.00002 $0.00029

Measured 9d ago against content hash b14695aba9a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

clean-journal 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 9d 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.

commands/clean-journal.md · 37 lines

What it actually says

creditgauge :clean-journal

Targets the append-only JSONL token-sample history files at state/<projectHash>/<sessionId>.jsonl. These accumulate over time and can use significant disk space.

Behavior

  • Default: removes .jsonl files older than 7 days
  • --days <N>: remove files older than N days
  • --all: remove ALL .jsonl journal files (use with caution)

Safety

  • Only removes files matching *.jsonl under state/<projectHash>/
  • Never touches diagnostics.jsonl, cache.json, or state.json
  • --dry-run previews what would be removed without deleting

Examples

# Preview what files older than 7 days would be removed
/creditgauge:clean-journal --dry-run

# Remove files older than 30 days
/creditgauge:clean-journal --days 30

# Remove every journal file
/creditgauge:clean-journal --all
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. 9d ago First seen · 37 lines · 18 tokens per session scan A b14695aba9a1

Subscribe to this mod's changes

clean-journal is a command published in the GitHub repository cwf818/creditgauge (2 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 286 once invoked, about $0.0001 per session on Opus 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-08-31.