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.
npx agentmods add commands/galando/temper/initgit clone --depth 1 https://github.com/galando/temperWhat 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 | $0.00019 | $0.00812 |
| Opus 5 | $0.00010 | $0.00406 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
init 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temper: Set Up This Project
Goal: get a project fully set up in one command. Seeds .claude/temper.config,
scaffolds .temper/, and installs the native commit gate — the one control that
physically blocks git commit while a gate is red. Idempotent: safe to run any number
of times; an existing config is never overwritten.
/temper runs this automatically the first time it's used in an un-set-up project, so
most people never call /temper:init by hand — it's here for an explicit re-run.
Steps
1. Resolve $CLAUDE_PLUGIN_ROOT (orchestrator-patterns.md → "$CLAUDE_PLUGIN_ROOT Resolution").
2. Config — .claude/temper.config:
a. EXISTS → report "Temper config already present" and do NOT overwrite it (it's the
user's). Check for retired v6.x blocks and report what's now ignored:
grep -nE '^(tokens|models|observability|capabilities|eval):' .claude/temper.config
Print one "NOTE: '{key}:' block found — retired, now ignored" line per match; if
none, print nothing. Read-only — never edits the file.
b. MISSING → mkdir -p .claude, copy
$CLAUDE_PLUGIN_ROOT/templates/temper.config.default → .claude/temper.config,
report "Created .claude/temper.config from the default template."
3. Scaffold — run `$CLAUDE_PLUGIN_ROOT/scripts/temper init` (creates .temper/: gates
ledger, overrides log, feedback-loops registry). Idempotent.
4. Commit gate — the headline guarantee. Run:
bash $CLAUDE_PLUGIN_ROOT/scripts/hooks/install.sh
It installs a native git pre-commit hook that runs `temper gate commit` (and the
secret scan) on every commit, fails open if temper isn't in use for a commit, and
backs up any existing non-Temper pre-commit hook first. It installs into the active
hooks dir — respecting an existing `core.hooksPath` (husky/lefthook) so the gate
isn't written where git would ignore it. Re-running is idempotent. If the project
isn't a git repo yet, install.sh exits non-zero — report "not a git repo yet; run
/temper:init again after `git init` to install the commit gate" and continue (the
config + scaffold still succeeded).
5. Report done, and name the one optional add-on in a single line:
"Set up. Optional: `/temper:pack enable hooks` adds edit-time guardrails (secret
blocking, frozen-path protection, auto-format, an approval prompt before overrides).
The commit gate above works without it."
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.
- yesterday First seen · 64 lines · 19 tokens per session scan A f2af5bda067a
init is a command published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 812 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.