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/buildgit 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.00008 | $0.00599 |
| Opus 5 | $0.00004 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
build 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build: Execute Plan
Goal: Implement approved plan task by task with TDD and graduated quality gates.
Execution
Full methodology: Read
$CLAUDE_PLUGIN_ROOT/reference/build.md
Subprocess Mode
If $CLAUDE_PLUGIN_ROOT/scripts/temper config get stages.subprocess false returns
true, don't run the methodology inline (skip the reference read and Quick Reference
below). Launch the same isolated subprocess /temper uses — model from temper model build, prompt: "Follow $CLAUDE_PLUGIN_ROOT/agents/build.md exactly. Spec:
.temper/specs/{feature-slug}. Standalone run — pass --spec-path
.temper/specs/{feature-slug} to every temper gate call." Print the returned box
verbatim, then run the gate + report per Deterministic Gate below (the subprocess
already recorded the RED/GREEN evidence and ticked tasks.md); auto-chain to
/temper:review → /temper:check as usual — the human gate stays in this context
either way.
Quick Reference
- Load plan from
.temper/specs/{feature}/tasks.md - Verify feature branch (create if on main)
- For each task: test from intent.md scenario (RED) → implement (GREEN) → validate
- Scenario coverage gate: every intent.md scenario must have a passing test
- Success criteria gate: code-validated criteria must be present (WARN only)
- Resumes interrupted builds from checkpoint
- After all tasks: run
temper gate build --spec-path .temper/specs/{feature-slug}— see Deterministic Gate below - Auto-chain → /temper:review → /temper:check
- Report results, ask to commit
Active Skills
- Temper Core — stack detection, pack resolution, quality gates
- Context Engineering — load hierarchical context at stage start (rules → arch → source → errors, under 2K lines/task)
- Source-Driven Development — before writing framework-specific code: detect installed version → fetch current docs → cite sources → surface API conflicts. Skip for plain logic or known patterns
Deterministic Gate
Follow $CLAUDE_PLUGIN_ROOT/agents/build.md steps 2-3 (record RED/GREEN test evidence
via temper evidence add --stage build --phase red|green) as you implement each task,
then run temper gate build --spec-path .temper/specs/{feature-slug} before reporting
results — same reason as Plan/Review/Check: skipping this leaves temper gate commit
unable to see that build happened at all. Pass --spec-path explicitly rather than
relying on temper state having been initialized.
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 · 53 lines · 8 tokens per session scan A f40c8f4f59e9
build is a command published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 599 once invoked, about $0.0000 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.