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/intentgit 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.00019 | $0.01122 |
| Opus 5 | $0.00010 | $0.00561 |
| Sonnet 5 | $0.00004 | $0.00224 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
intent 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent: Capture an Idea as an Artifact
Goal: Turn an idea, a ticket, or an incident finding into a committed
.temper/specs/{slug}/intent.md with Status: draft — and stop there. This is the
entry point for work that isn't ready to build yet: the originator (who may not be the
implementer, or an engineer at all) describes the problem in their own words; the
committed draft is what a product owner reviews and what /temper later picks up.
/temper's own Intent stage (and standalone /temper:plan) still creates intent.md
when none exists — this command exists for the capture-now-build-later split, so the
idea's author, timestamp, and revision history live in version control from the moment
it's real. A draft captured here is exactly what the pipeline's Intent gate later
presents for acceptance.
Usage
/temper:intent "handlers spend a third of call time on status-only queries"
/temper:intent "JIRA-4521" # fetch the ticket, capture it as intent
/temper:intent # no argument — interview from scratch
Execution
-
Understand the problem, not the solution. Read
$ARGUMENTS(detect Jira/GitHub/free-text the same way/temper:planPhase 0 does). Then ask what an analyst would ask — scope, who is affected, what better looks like, what is out of scope — viaAskUserQuestion, max 2-3 concrete rounds. No formal language is required of the originator; producing structure is your job, not theirs. -
Write the draft to
.temper/specs/{slug}/intent.mdusing$CLAUDE_PLUGIN_ROOT/templates/intent.md:- Header:
**Author:**(fromgit config user.name/user.email),**Status:** draft,**Created:**,**Ticket:**if one was given. - Fill Problem, Success Criteria (measurable, each with a
Validate:type), Constraints, Target Users, and Open Questions (every unresolved point from step 1 — carrying a question forward honestly beats resolving it by guess). - Do not write Scenarios or pick an architecture. BDD scenarios are derived
from the measured blast radius at Plan time (
reference/plan.md), not at capture time. Leave the Scenarios section as the template's placeholder.
- Header:
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 · 83 lines · 19 tokens per session scan A 8a91a95aaeae
intent is a command published in the GitHub repository galando/temper (15 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 1,122 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.