runs

runs is a skill for Claude Code from ai-analyst-lab/ai-analyst. It costs 229 tokens per session (2,460 once invoked), scanned C, original, MIT.

A tool for browsing and managing past analysis runs. A run is one execution of an analysis, including its files, results, progress, and errors.

In plain words
What is it for?
Use it to list runs, inspect their status and outputs, compare analyses, and clean up old run files.
Why use it?
It prevents analysis history from being split between active work and completed archives. It helps you find the work you need without searching folders manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to list runs, inspect their status and outputs, compare analyses, and clean up old run files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ai-analyst-lab/ai-analyst/runs
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.

Any agent
npx skills add ai-analyst-lab/ai-analyst --skill runs
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst

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.

agentmods badge for runs

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/runs/github.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/runs)
Your own site
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/runs"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/runs/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 runs

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/runs"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/runs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 229 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,460 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00229 $0.02460
Opus 5 $0.00114 $0.01230
Sonnet 5 $0.00046 $0.00492
Haiku 4.5 $0.00023 $0.00246

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

Security

Grade C, and why

runs scanned grade C 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 2d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

3. On confirmation, remove the directories using `rm -rf`
.claude/skills/runs/SKILL.md · 219 lines

How it starts

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

Skill: Runs

Purpose

Browse, inspect, compare, and clean up past pipeline runs. Each run is a self-contained directory under working/runs/ with its own working files, outputs, and pipeline state.

Architecture: Understanding the Two-Source System

The AI Analyst tracks analysis work in two independent locations:

  1. Active Pipeline Runs (working/runs/)

    • Contains in-progress, recently completed, or failed pipeline executions
    • Each run is a directory with pipeline_state.json tracking agent progress
    • Used for resuming interrupted work and debugging issues
    • Cleaned up periodically (30-day retention by default)
  2. Archived Analyses (.knowledge/analyses/)

    • Contains completed analyses that have been formally archived
    • Includes validation grades, key findings, and links to outputs
    • Permanent knowledge base for organizational learning
    • Survives even after working/runs/ cleanup

Why this matters: A user asking "what analyses have I run?" expects to see BOTH in-progress work (working/runs/) AND completed archived work (.knowledge/analyses/). Missing either source gives an incomplete picture.

When to Use

  • User says /runs, /runs list, /runs latest, /runs clean, or /runs compare
  • When the user wants to see what analyses have been executed

Invocation

  • /runs or /runs list -- list all past runs
  • /runs latest -- show details of the most recent run
  • /runs {id} -- show details of a specific run (partial match supported)
  • /runs clean -- remove runs older than 30 days (confirmation required)
  • /runs compare {id1} {id2} -- compare two runs side by side

Instructions

Step 1: Determine Command Type

Parse the user's command to understand which operation they want:

  • List: /runs or /runs list → requires dual-source scanning
  • Latest: /runs latest → single source (working/latest symlink)
  • Detail: /runs {id} → single source (working/runs/)
  • Compare: /runs compare {id1} {id2} → single source (working/runs/)
  • Clean: /runs clean → single source (working/runs/)

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

  1. 2d ago First seen · 219 lines · 229 tokens per session scan C 344a02d92999

Subscribe to this mod's changes

runs is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 229 tokens to every session and 2,460 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens