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/statusgit 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.00011 | $0.00600 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
status 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status: Quality Metrics Dashboard
Goal: Display metrics, trends, learning loop suggestions, and observability data.
Execution
Full methodology: Read
$CLAUDE_PLUGIN_ROOT/reference/status.md
Quick Reference
- Initialize
.temper/directory if missing (metrics, review-memory, specs/) - Read
.temper/metrics.json+.temper/review-memory.json - Read
.temper/gates.json+.temper/evidence/*.json(the current/last run's evidence-backed gate ledger — run$CLAUDE_PLUGIN_ROOT/scripts/temper report, or read the files directly) - Read
.temper/feedback-loops.json(if exists — active feedback loop state) 4.5. Run$CLAUDE_PLUGIN_ROOT/scripts/temper bands(deterministic control-band drift check over metrics history — CONTROL BANDS section; apropose-tier breach offers drafting an intent.md, see reference/status.md Step 3.7) - Detect MCP tools: attempt to call
get_impact_radius_tool(code-review-graph) and check if semgrep tools are available. Report availability in dashboard. - Display: reviews, quality trend, debt, hotspots, top patterns, learning loop, active specs, MCP TOOLS section, GATE LEDGER section, FEEDBACK LOOPS section, CONTROL BANDS section
- If pattern count >= 3: suggest auto-rule
- Hotspot map: shows which files generate the most issues
Gate Ledger Panel (v7 — replaces the v6.x Observability/Economics panels)
v6.x rendered per-stage cost/latency/token estimates here — numbers with no mechanical
backing, exactly what v7 stops presenting as fact. v7 shows only what temper gate and
temper evidence actually recorded:
GATE LEDGER
{output of: $CLAUDE_PLUGIN_ROOT/scripts/temper report}
Evidence: {N} PROVEN, {N} HEURISTIC, {N} SEMANTIC (this run)
Graceful absence: if .temper/gates.json does not exist, print "No gate data yet. Run /temper to populate it." Do not error.
Feedback Loops Section (v4.0.0)
If .temper/feedback-loops.json exists and feedback.enabled: true in temper.config, show:
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 · 58 lines · 11 tokens per session scan A e0d03d7b8a2d
status is a command published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 600 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.