A command that displays project quality metrics, trends, review history, active specifications, and observability data in a dashboard. It also checks available supporting tools and evidence from recent quality gates.

Use it to inspect metrics files, review memory, gate results, feedback loops, control-band drift, and available code-analysis tools.

It puts information about code quality, technical debt, recurring problems, and review results in one view. This helps identify areas that may need attention and track whether quality is improving.

status — Command for Claude Code by galando/temper

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add galando/temper

Claude Code

/plugin install temper

Made for: Claude Code.

Or install temper, the plugin that ships this one along with the rest of its 5 skills, 11 commands, 11 agents, 2 hooks.

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/galando/temper/status/github.svg)](https://agentmods.dev/commands/galando/temper/status)

Your own site

<a href="https://agentmods.dev/commands/galando/temper/status"><img src="https://agentmods.dev/badge/commands/galando/temper/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/galando/temper/status"><img src="https://agentmods.dev/badge/commands/galando/temper/status.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 749 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.00749
Opus 5.5	$0.00004	$0.00300
Sonnet 5.5	$0.00002	$0.00150
Haiku 4.5	$0.00001	$0.00075

Measured 4d ago against content hash 69af17d462d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 4d 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.

commands/status.md · 64 lines

How it starts

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

Status: Quality Metrics Dashboard

Goal: Display metrics, trends, learning loop suggestions, and observability data.

Execution

Full methodology: Read ${CLAUDE_PLUGIN_ROOT}/reference/status.md

Plugin folder: the folder that holds ${CLAUDE_PLUGIN_ROOT}/scripts/temper (that path with /scripts/temper taken off). Wherever a reference page or a brief writes the CLAUDE_PLUGIN_ROOT variable, use this folder.

Quick Reference

Initialize .temper/ directory if missing (metrics, review-memory, specs/)
Read .temper/metrics.json + .temper/review-memory.json
Read .temper/gates.json and the evidence ledger (the current/last run's evidence-backed gate ledger) through ${CLAUDE_PLUGIN_ROOT}/scripts/temper report
Read .temper/feedback-loops.json (if exists — active feedback loop state) 4.2. If the current spec has an intent.md, run ${CLAUDE_PLUGIN_ROOT}/scripts/temper status (per-criterion passed/open with evidence; --json writes .temper/status.json) 4.5. Run ${CLAUDE_PLUGIN_ROOT}/scripts/temper bands (deterministic control-band drift check over metrics history — CONTROL BANDS section; a propose-tier breach offers drafting an intent.md, see ${CLAUDE_PLUGIN_ROOT}/reference/status.md Step 3.7) 4.7. Run ${CLAUDE_PLUGIN_ROOT}/scripts/temper drift (add --run when the person asks to run each finished scenario test; read only: each finished spec compared with the tree as it is now; SPEC DRIFT section, printed as it comes: missing file, test gone, changed since)
Detect MCP tools: attempt to call get_impact_radius_tool (code-review-graph) and check if semgrep tools are available. Report availability in dashboard.
Display: reviews, quality trend, debt, hotspots, top patterns, learning loop, active specs, MCP TOOLS section, GATE LEDGER section, FEEDBACK LOOPS section, CONTROL BANDS section, SPEC DRIFT section
If pattern count >= 3: suggest auto-rule
Hotspot map: shows which files generate the most issues

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

4d ago Changed · +2 lines 69af17d462d8
1mo ago Changed · +3 lines 29b4da411182
1mo ago Changed · +2 lines f448dc436f67
1mo ago Changed 0d55a873d572
2mo ago Changed · -1 lines 88f829d8a970
2mo ago First seen · 58 lines · 11 tokens per session scan A e0d03d7b8a2d

Subscribe to this mod's changes

status is a command published in the GitHub repository galando/temper (18 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 749 once invoked, about $0.0000 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.

Analytics and metrics

status next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
statusgalando/temper	Command	18	yesterday	MIT	A	11	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code