Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/.claude/commands/whats-happening.mdgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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.
[](https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/whats-happening)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/whats-happening"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/whats-happening/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.
<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/whats-happening"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/whats-happening.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00816 |
| Opus 5.5 | $0.00000 | $0.00326 |
| Sonnet 5.5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
whats-happening 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/whats-happening
Observe a different Claude session that may be running forever on a prompt, and report what its current turn is doing. It reads that session's live transcript off disk — it does not interrupt or query the busy session (a busy session can't answer a slash command mid-turn).
DEV-ONLY: gated out of user installs (DEV_ONLY_FILES in bin/cli.js), dogfooded from the CCA
repo like token-guard. Scope is the two reliable outputs — what the turn is doing right now
and time spent per activity. "Still plans to do" and an ETA are deferred (only knowable if the
target wrote a plan/TaskList; often absent).
Step 1 — run the observer
$ARGUMENTS is a substring of the target session's tab title (the text after the state glyph).
-
If
$ARGUMENTSis empty, run the list form so the user can see which sessions are live and grab a title:node "${CLAUDE_PROJECT_DIR:-.}/.claude/scripts/whats-happening.js" --list -
Otherwise, pass the title substring (quote it — titles contain spaces and the em-dash):
node "${CLAUDE_PROJECT_DIR:-.}/.claude/scripts/whats-happening.js" "$ARGUMENTS"
The script auto-excludes the current session (via CLAUDE_CODE_SESSION_ID), so it never reports
on itself.
Step 2 — relay the output
The script prints ready-to-read Markdown. Relay it as-is — don't re-summarize. The two headline signals:
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 · 63 lines · 0 tokens per session scan A 54638ba66221
whats-happening is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 816 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.
Other commands, from other repositories
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
gws-people
Search and look up Google Contacts and directory profiles.
check
Run a quick scan of the memory system's health. For daily use.