A demo command that runs the main features of the who-ran-what command-line tool. It displays activity summaries, statistics, project views, and cleanup suggestions.

Use it to view weekly, daily, or monthly activity; inspect agent, skill, and project usage; find unused items; and check the current project's status.

It provides a quick way to learn what the tool reports, check changes after development, or show its behavior to someone else.

How mylee04/who-ran-what configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mylee04/who-ran-what. 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/mylee04/who-ran-what/main/.claude/commands/demo.md

Clone the repo

git clone --depth 1 https://github.com/mylee04/who-ran-what

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/mylee04/who-ran-what/demo/github.svg)](https://agentmods.dev/commands/mylee04/who-ran-what/demo)

Your own site

<a href="https://agentmods.dev/commands/mylee04/who-ran-what/demo"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/demo/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/mylee04/who-ran-what/demo"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/demo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 349 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.00011	$0.00349
Opus 5	$0.00005	$0.00175
Sonnet 5	$0.00002	$0.00070
Haiku 4.5	$0.00001	$0.00035

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

Security

Grade A, and why

demo 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 11d 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/demo.md · 83 lines

What it actually says

Demo Mode

What This Command Does

Runs through all main features to demonstrate the tool's capabilities.

Demo Script

1. Show Version and Help

echo "=== who-ran-what Demo ==="
echo ""

echo "1. Version"
./bin/who-ran-what version
echo ""

echo "2. Help"
./bin/who-ran-what help
echo ""

2. Dashboard Views

echo "3. Weekly Dashboard (default)"
./bin/who-ran-what
echo ""

echo "4. Today's Activity"
./bin/who-ran-what today
echo ""

echo "5. Monthly Overview"
./bin/who-ran-what month
echo ""

3. Detailed Stats

echo "6. Agent Statistics"
./bin/who-ran-what agents
echo ""

echo "7. Skill Usage"
./bin/who-ran-what skills
echo ""

echo "8. Project Breakdown"
./bin/who-ran-what projects
echo ""

4. Cleanup Suggestions

echo "9. Unused Items (cleanup suggestions)"
./bin/who-ran-what clean
echo ""

5. Project-Specific Commands

echo "10. Current Project Status"
./bin/who-ran-what project
echo ""

Usage

Run this demo to see all features in action. Useful for:

Learning what the tool can do
Testing after changes
Showing the tool to others

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.

11d ago First seen · 83 lines · 11 tokens per session scan A c561a1a3d66f

Subscribe to this mod's changes

demo is a command published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 349 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.

ai claude cli codex developer-tools

atomic-plan

Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.

damusix/atomic-claude · 54 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

session-report

Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.

damusix/atomic-claude · 31 tokens

Suggest the most likely next workflow action based on current context.

jayvee/aigon · 11 tokens

afo

Open feature worktree in terminal and start agent (shortcut for feature-open).

jayvee/aigon · 15 tokens

advanced-code-review-context

Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.

axiomantic/spellbook · 19 tokens

who-ran-what: Command for Claude Code