What is system:status?

A command that shows the current state of your work, Git repository, computer setup, and saved project memory in one view. Git is the system commonly used to track code changes and branches.

Use it to review active work units, Git changes, recent commits, framework and memory status, and suggested next steps.

It gives you a quick way to see what work is active, what files have changed, and what the project suggests doing next.

system:status — Command for Claude Code by stefan-jansen

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.

Clone the repo

git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkit

Made for: Claude Code.

Or install system, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 2 agents.

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/stefan-jansen/claude-code-toolkit/system-status/github.svg)](https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/system-status)

Your own site

<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/system-status"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/system-status/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/stefan-jansen/claude-code-toolkit/system-status"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/system-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 329 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.00014	$0.00329
Opus 5.5	$0.00006	$0.00132
Sonnet 5.5	$0.00003	$0.00066
Haiku 4.5	$0.00001	$0.00033

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

Security

Grade A, and why

system:status 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 1mo 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.

plugins/system/commands/system:status.md · 63 lines

What it actually says

System Status

Comprehensive view of work state, git status, and system health.

Input: $ARGUMENTS

Usage

/status           # Quick overview
/status verbose   # Extended information

Output Sections

📋 WORK STATUS

🟢 Active: [work-unit-id]
   Phase: exploring|planning|implementing
   Task: TASK-003
   Total units: 5

🔀 GIT STATUS

🌳 Branch: main
📝 Changes: 3 modified, 1 staged, 2 untracked
📥 Last: abc123 - feat: add auth (2 hours ago)

⚙️ SYSTEM STATUS

🏗️  Framework: Claude Code v3.0 ✅
💾 Memory: 5 files, 24KB

🧠 MEMORY STATUS (verbose only)

🔄 Recent updates: 2 files in last hour
🔗 Transitions: 5 saved

🎯 NEXT STEPS

➡️ Continue with: /next
➡️ Commit changes: /git commit

Checks Performed

Active work unit in .claude/work/ACTIVE_WORK
Work unit state from state.json
Git branch and changes
Framework directory structure
Memory file count and size

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.

1mo ago First seen · 63 lines · 14 tokens per session scan A b36384cf811a

Subscribe to this mod's changes

system:status is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (89 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 329 once invoked, about $0.0001 per session on Opus 5.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-30.

Claude Code Memory and context Productivity agents anthropic coding-agents framework plugins

system:status