A validation command that detects a project's technology stack and runs its configured checks in sequence. A stack means the languages, frameworks, tools, and services used by a project.

Use it to check the environment, compile or build the project, run unit and integration tests, measure coverage, apply formatting and lint rules, check types, and scan dependencies for security issues.

It gathers common checks in one pipeline and stops when an earlier check fails, making validation failures easier to locate.

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

Your own site

<a href="https://agentmods.dev/commands/galando/temper/check"><img src="https://agentmods.dev/badge/commands/galando/temper/check/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/check"><img src="https://agentmods.dev/badge/commands/galando/temper/check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 224 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.00017	$0.00224
Opus 5.5	$0.00007	$0.00090
Sonnet 5.5	$0.00003	$0.00045
Haiku 4.5	$0.00002	$0.00022

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

Security

Grade A, and why

check 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 22d 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/check.md · 18 lines

What it actually says

Check

This command is a door into /temper: it starts a run at Check, or takes up the run that is active, and from there everything happens as /temper does it. There is one flow, and it is ${CLAUDE_PLUGIN_ROOT}/commands/temper.md.

Read ${CLAUDE_PLUGIN_ROOT}/commands/temper.md now and follow it exactly, entering at Check as its section "Entering at a stage" says, with $ARGUMENTS as the spec folder's name. That file was not filled in when you read it: wherever it writes the CLAUDE_PLUGIN_ROOT variable, use the folder that holds ${CLAUDE_PLUGIN_ROOT}/scripts/temper (that path with /scripts/temper taken off), and wherever it writes the ARGUMENTS variable, use $ARGUMENTS. Its first instruction (the enforcement line) applies here too.

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.

22d ago Changed · -63 lines · +12 tokens per session e0c7cc4597fa
1mo ago Changed · +20 lines 96199f552115
2mo ago Changed b836912ad29e
2mo ago First seen · 61 lines · 5 tokens per session scan A 2f8a0df162d1

Subscribe to this mod's changes

check is a command published in the GitHub repository galando/temper (18 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 224 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.

check next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
checkgalando/temper	Command	18	yesterday	MIT	A	17	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