A command for managing quality packs, which are groups of project rules and workflow settings.

Use it to list packs, turn them on or off, create launchers, and configure their linked files and workflow phases.

It removes the need to check pack files and configuration manually to see which packs are active, where they came from, and whether their links work.

pack — Command by galando

Install

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.

agentmods

npx agentmods add commands/galando/temper/pack

Clone the repo

git clone --depth 1 https://github.com/galando/temper

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,116 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What 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.00017	$0.01116
Opus 5	$0.00009	$0.00558
Sonnet 5	$0.00003	$0.00223
Haiku 4.5	$0.00002	$0.00112

Measured 2d ago against content hash 5a4aca0e9283, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pack 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.

commands/pack.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pack: Quality Pack Manager

Step 1: Discover Packs

Read .claude/temper.config packs section. Scan three tiers:

.claude/packs/{name}/rules.md (project-local, highest priority)
~/.claude/packs/{name}/rules.md (global)
$CLAUDE_PLUGIN_ROOT/packs/{name}/rules.md (built-in)

Deduplicate by name (highest tier wins). For each pack: read rules.md header, check enabled status, read phases and link from config.

Step 2: Display Pack Table

Build the table dynamically from discovered packs. Do NOT use hardcoded example rows.

Format each row using actual data:

NAME — pack name from config
STATUS — ON if in packs list, OFF if not
PHASES — from config (show all if not specified)
LINK — from config (show — if none)
CONNECTED — check if link target actually exists on filesystem

Example structure (populate with real data only):

┌──────────────────────────────────────────────────────────────────────────┐
│ PACK — Quality Pack Manager                                      v4.4.0 │
├──────────────────────────────────────────────────────────────────────────┤
│  NAME            STATUS  PHASES     LINK                CONNECTED        │
│  ────────────── ─────── ────────── ─────────────────── ──────────────── │
│  {name}           {on}    {phases}   {link}              {found/missing} │
│  ...                                                                     │
│  N packs total (X enabled, Y disabled)                                   │
└──────────────────────────────────────────────────────────────────────────┘

Step 3: AskUserQuestion (max 4 options)

AskUserQuestion:
  question: "What would you like to do?"
  options:
    - label: "Toggle packs on/off"
      description: "Select packs to enable or disable."
    - label: "Quick-create launcher pack"
      description: "Wrap a plugin or skill as a BLOCK-level pack."
    - label: "Configure pack (link, phases)"
      description: "Set link target or phase scoping for an existing pack."
    - label: "Done"
      description: "Exit. Use 'Other' for full interactive pack builder."
  multiSelect: false

Read the full file on GitHub · 125 lines

Changes

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 · 125 lines · 17 tokens per session scan A 5a4aca0e9283

Subscribe to this mod's changes

pack is a command published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 1,116 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.

Productivity

pack

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Pack: Quality Pack Manager

Step 1: Discover Packs

Step 2: Display Pack Table

Step 3: AskUserQuestion (max 4 options)

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement