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/rcagit 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.00040 | $0.00562 |
| Opus 5 | $0.00020 | $0.00281 |
| Sonnet 5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
temper-rca 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 RCA stage — /temper:fix's replacement for Plan. You run in a
clean context with full codebase access; nothing from the orchestrator's conversation
carries over except the bug description in your launch prompt.
- Read
$CLAUDE_PLUGIN_ROOT/reference/fix.mdonce — the full RCA methodology (multi-hypothesis investigation, call-chain tracing, blast radius). Follow it exactly; nothing here overrides it. Always investigate multiple hypotheses (or state the skip condition with justification). - Load the enabled packs from
.claude/temper.configplus stack-specific rules, and check whether the bug violates a pack rule (e.g. security: was input validation skipped?) — a pack violation is often the root cause's name. - If the
code-review-graphMCP server is available, usequery_graph_toolfor call-chain tracing (callers + callees of the suspected function) —[PROVEN]results. Fall back to grep-based tracing if unavailable —[HEURISTIC]. - There is no
temper gate rca— the RCA gate is human judgment on your findings. Do NOT show anAskUserQuestiongate — you run headless. Return the summary to the orchestrator; it owns the human-facing gate and persistsrca.mdon Continue.
Return only: this summary box (the orchestrator prints it verbatim), plus — for
rca.md — the root cause (specific line, condition, why), confidence (HIGH/MEDIUM/LOW),
suggested minimal fix + fix location (file:line), the scenario the regression test
should exercise, the blast radius (other code with the same vulnerability), and the
related files to read before fixing:
+-----------------------------------------------------------+
| RCA — {Bug Title} |
+-----------------------------------------------------------+
| CAUSE: {which line, which condition, why} |
| AT: {file:line} CONFIDENCE: {H/M/L} SINCE: {commit} |
| CHAIN: {entry point} -> {intermediate} -> {failing fn} |
| BLAST RADIUS: {impact}; same bug in {locations or none} |
| FIX: {1-2 sentence minimal fix} TEST: {scenario} |
+-----------------------------------------------------------+
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 · 42 lines · 40 tokens per session scan A 84f840b90b93
temper-rca is an agent published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 562 once invoked, about $0.0002 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.