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 skills/galando/temper/temper-corenpx skills add galando/temper --skill temper-coregit 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.00014 | $0.00819 |
| Opus 5 | $0.00007 | $0.00409 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
temper-core 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temper Core
Stack detection → Quality gates (SUGGEST/WARN/BLOCK) → Confidence scoring (0.0-1.0) → Review memory → Metrics.
Stack Detection
.claude/temper.config→stackfield.claude/presets/*.yaml→stacksection- Auto-detect: pom.xml→Spring Boot, package.json→Node, pyproject.toml→Python, go.mod→Go, Cargo.toml→Rust
- Load
.claude/packs/stacks/{stack}.md
Pack Resolution (v4.3.0)
Three-tier: project-local > global > built-in. Read live (no cache) by every stage command (build, review, check, plan, design) for phase-filtered loading.
.claude/packs/{name}/rules.md(project)~/.claude/packs/{name}/rules.md(global)$CLAUDE_PLUGIN_ROOT/packs/{name}/rules.md(built-in) Packs supportlink: plugin://name | skill://nameandphases: [build, review, ...]— declared in the pack'srules.mdfrontmatter, overridable per project on thepacks:config entry, defaulting toallwhen neither says.[]means no stage loads it. Precedence and rationale:reference/pack.md→ "Pack Configuration Schema".
Quality Gates
- SUGGEST: Non-blocking
- WARN: Highlighted, developer decides
- BLOCK: Must fix (security/architecture only)
Confidence & Memory
- Threshold: 0.7 (configurable)
- Review memory:
.temper/review-memory.json— auto-suppress after 5 dismissals - Metrics:
.temper/metrics.json
Review memory — the one finding memory
Reviews get smarter over time through a single store, .temper/review-memory.json
(there is no separate learning file). Written by /temper:review, surfaced at
/temper:status.
| Capability | Trigger | Action |
|---|---|---|
| Pattern tracking | every review | Cluster findings by category + file-path prefix + keywords into patterns[key] |
| Rule promotion | accepted 3+ times @ ≥70% (5+ @ ≥80% for security/architecture → BLOCK) | Suggest a pack rule at /temper:status; the human accepts BLOCK/WARN |
| Noise reduction | dismissed 3+ (downgrade) / 5+ (suppress) | Downgrade or auto-suppress, per-context |
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 · 66 lines · 14 tokens per session scan A 93c7124fe3f7
temper-core is a skill published in the GitHub repository galando/temper (16 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 819 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.