What is pipeline-history?

A command that lists earlier pipeline runs from the project's recorded history, including cost, token use, cache use, and status.

Use it to review recent runs, show all runs, filter completed or halted runs, or export the validated history as JSON.

It gives you a quick view of what ran and whether it completed or stopped, without opening several history files by hand.

How TheAstrelo/Claude-Pipeline configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/TheAstrelo/Claude-Pipeline/main/.claude/commands/pipeline-history.md

Clone the repo

git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

Made for: Claude Code.

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/commands/theastrelo/claude-pipeline/pipeline-history/github.svg)](https://agentmods.dev/commands/theastrelo/claude-pipeline/pipeline-history)

Your own site

<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/pipeline-history"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pipeline-history/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/commands/theastrelo/claude-pipeline/pipeline-history"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pipeline-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 974 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.00000	$0.00974
Opus 5.5	$0.00000	$0.00390
Sonnet 5.5	$0.00000	$0.00195
Haiku 4.5	$0.00000	$0.00097

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

Security

Grade A, and why

pipeline-history 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 2mo 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.

.claude/commands/pipeline-history.md · 130 lines

How it starts

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

Pipeline History Command

Show past pipeline runs with cost, token, cache, and status summaries.

Arguments

$ARGUMENTS - Optional flags:
- --all - Show all history (not just the last 10)
- --json - Output the schema-2 history document as JSON
- --failed - Show only HALTED runs
- --success - Show only COMPLETED runs

Instructions

1. Load and Validate History

Read .pipeline/history.json.

If it does not exist, output No pipeline history found. and exit.

Parse schemaVersion. Accept major version 2 and tolerate additive minor fields. Reject any other major version and tell the user to use a compatible history reader. Never reinterpret an unknown schema.

The file is a derived index, not durable evidence. Each run's authoritative record is .pipeline/artifacts/<session>/ledger.jsonl; its run.json is a derived per-run summary. Do not edit any of these files from this command.

2. Parse Arguments

--all: do not limit results
--json: output the validated JSON document
--failed: filter status = "HALTED"
--success: filter status = "COMPLETED"

RUNNING means no terminal event follows the latest start/resume event. It is neither a successful nor a failed run.

3. Filter and Sort

Sort runs by finishedAt, newest first.
Apply the requested status filter.
Limit to 10 unless --all is present.

4. Calculate Totals

For the displayed set report:

Total runs
Completed, halted, and running counts
Completion rate
Total estimated/reported cost
Total input plus output tokens
Cached input tokens

5. Format Output

Default table:

Pipeline History (last 10 runs)

  #  Status     Task                         Cost      Tokens   Cached
  1  COMPLETED  add user authentication      $0.2400    15,000    4,000
  2  HALTED     implement payment flow       $0.1500     9,400        0
  3  RUNNING    add dashboard widget         $0.0800     5,200    1,100

Summary:
  Runs: 3  Completed: 1  Halted: 1  Running: 1
  Cost: $0.4700  Tokens: 29,600  Cached: 5,100

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

2mo ago First seen · 130 lines · 0 tokens per session scan A f07cd06b43d0

Subscribe to this mod's changes

pipeline-history is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 974 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-30.

Analytics and metrics agentic ai-agents aider anthropic automation claude

scout-meta-review

Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.

Raven-Scout/Scout · 61 tokens

Claude-Pipeline: Command for Claude Code