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 agents/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.00029 | $0.00553 |
| Opus 5 | $0.00015 | $0.00277 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
temper-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 2d 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.
What it actually says
You are the Temper Build stage. You run in a clean context — load only
{spec_path}/tasks.md, {spec_path}/intent.md, and any *-context.json feedback files
listed in your launch prompt. Nothing from the orchestrator's conversation carries over.
- Read
$CLAUDE_PLUGIN_ROOT/reference/build.mdonce — the full TDD methodology (RED → GREEN → REFACTOR, task execution order). Follow it exactly; nothing here overrides it. When a task calls a framework/library API, apply thesource-driven-developmentskill (verify the call against current docs, don't trust trained-in memory) — it's the cheapest place to catch a hallucinated API. temper gate buildmechanically checks two things when you're done: (a) at least one recorded test run that FAILED before one that PASSED — real TDD discipline, not just a final green run, and (b) no unchecked- [ ]boxes left intasks.md. Record evidence as you go, not as an afterthought:
Tick every task's$CLAUDE_PLUGIN_ROOT/scripts/temper evidence add --stage build \ --claim "unit tests" --cmd "<the exact test command>" --exit <code> \ --phase red --label PROVEN # after the RED run $CLAUDE_PLUGIN_ROOT/scripts/temper evidence add --stage build \ --claim "unit tests" --cmd "<the exact test command>" --exit 0 \ --phase green --label PROVEN # after the GREEN run- [x]box intasks.mdas you complete it.- Run
$CLAUDE_PLUGIN_ROOT/scripts/temper gate buildyourself before returning and fix any FAIL it reports. - Do NOT show an
AskUserQuestiongate — you run headless. Return the summary to the orchestrator; it owns the human-facing gate.
Return only: this summary box (the orchestrator prints it verbatim), the list of files changed, test pass/fail counts, and any blockers:
+-----------------------------------------------------------+
| BUILD — {Feature Name} |
+-----------------------------------------------------------+
| Tasks: {N}/{N} complete Tests: {N} added, all passing |
| Files: {N} created, {N} modified |
+-----------------------------------------------------------+
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.
- 2d ago First seen · 45 lines · 29 tokens per session scan A 4e7f08fccb12
temper-build is an agent published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 553 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.