A code-review and build-planning guide that detects the project's programming stack, applies quality checks, scores confidence, and remembers review information.

Use it when building, reviewing, checking, planning, or designing changes across projects using Java, Node.js, Python, Go, or Rust.

It helps match checks and review rules to the technologies in the repository, while highlighting issues by severity.

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

Your own site

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

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,576 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.01576
Opus 5.5	$0.00007	$0.00630
Sonnet 5.5	$0.00003	$0.00315
Haiku 4.5	$0.00002	$0.00158

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

Security

Grade A, and why

temper-core 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.

skills/temper-core/SKILL.md · 96 lines

How it starts

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

Temper Core

Stack detection → Quality gates (SUGGEST/WARN/BLOCK) → Confidence scoring (0.0-1.0) → Review memory → Metrics.

Enforcement marker. Look for a line in your system prompt that starts with Temper enforcement:. With no such line, make the very first sentence of your first reply in this conversation, before anything else and also when the arguments of /temper:temper start with one of its reserved first words (such as status, report, help or approve), exactly "Temper enforcement is off here (no mods support); continuing with prompt based phases.". With the line Temper enforcement: off (UI only), the Temper mod is loaded and the user turned enforcement off: make that first sentence exactly "Temper enforcement is off (turned off by the user); continuing with prompt based phases." instead. Then carry on exactly as written below. Never treat either case as an error and do not mention it again. With Temper enforcement: active, say nothing about it. Skip this paragraph when you run as a stage subprocess (your launch prompt has a Plugin folder: line): a subprocess's system prompt never has that line, and the orchestrator or the standalone command states enforcement once, in the main conversation.

Stack Detection

.claude/temper.config → stack field
The YAML preset files in the project's .claude/presets folder (list the folder) → stack section
Auto-detect: pom.xml→Spring Boot, package.json→Node, pyproject.toml→Python, go.mod→Go, Cargo.toml→Rust
Load .claude/packs/stacks/{stack}.md

Pack Resolution

Three-tier: project-local > global > built-in. Read live (no cache) by every stage command (build, review, check, plan, design) for phase-filtered loading.

.claude/packs/{name}/rules.md (project)
~/.claude/packs/{name}/rules.md (global)
built-in, exactly these files: ${CLAUDE_PLUGIN_ROOT}/packs/quality/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/tdd/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/security/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/git/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/performance/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/api-design/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/architecture-depth/rules.md, ${CLAUDE_PLUGIN_ROOT}/packs/guardrails/rules.md

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

22d ago Changed · +2 lines 6c1517013f7b
1mo ago Changed · +22 lines ebb1a1af7ced
1mo ago Changed · +5 lines b65097a9005d
1mo ago Changed 57806c90a569
1mo ago Changed 3c51f68e2911
1mo ago Changed · +2 lines · +3 tokens per session 7cb857c3ee6a
2mo ago Changed · -1 lines 2fcc46c4d643
2mo ago First seen · 66 lines · 14 tokens per session scan A 93c7124fe3f7

Subscribe to this mod's changes

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

Code review

temper-core next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
temper-coregalando/temper	Skill	18	yesterday	MIT	A	17	Claude Code
autoreviewopenclaw/clawhub	Skill	9.5k	yesterday	MIT	A	17	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	6d ago	MIT	A	115	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.2k	yesterday	MIT	A	48	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	945	yesterday	MIT	A	84	Claude Code
explore-unknownsdzhng/skills	Skill	1.4k	2d ago	MIT	A	162	Claude Code, Codex
re0-mergeLilMGenius/paperthin	Skill	1.4k	4d ago	MIT	A	70	Claude Code