workflow

workflow is a command for Claude Code from gotempsh/temps. It costs 0 tokens per session (513 once invoked), scanned A, original, Apache-2.0.

A command-line tool for listing and running workflows or agents, which are predefined automated processes for a project.

In plain words
What is it for?
List available workflows, run one with a text context or error-group link, stream its output, or run a temporary workflow from a local YAML file.
Why use it?
It lets you trigger automation and inspect its output without switching to another interface.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

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/gotempsh/temps/workflow
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workflow

README.md
[![agentmods](https://agentmods.dev/badge/commands/gotempsh/temps/workflow.svg)](https://agentmods.dev/commands/gotempsh/temps/workflow)
Your own site
<a href="https://agentmods.dev/commands/gotempsh/temps/workflow"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 513 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00513
Opus 5 $0.00000 $0.00257
Sonnet 5 $0.00000 $0.00103
Haiku 4.5 $0.00000 $0.00051

Measured 2d ago against content hash 40246941e611, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

skills/temps/references/commands/workflow.md · 43 lines

What it actually says

workflow command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

workflow (alias: wf)

Trigger and inspect agent/workflow runs

Subcommands:

  • list (ls) - List workflows/agents available on this project
  • run - Trigger a workflow and stream its output

workflow list (alias: ls)

List workflows/agents available on this project

Options:

Flag Description Default Required
-p, --project <slug> Project slug (auto-detect from .temps/config.json) - No
--json Output as JSON - No

workflow run

Trigger a workflow and stream its output

Options:

Flag Description Default Required
-p, --project <slug> Project slug (auto-detect from .temps/config.json) - No
-c, --context <text> Free-form user context passed to the workflow (e.g. a bug description) - No
-f, --from-file <path> Run an ephemeral workflow from a local YAML file (no server-side persistence). Mutually exclusive with . - No
-e, --error-group <id> Link this run to an error group id. The workflow will see the error type, message, and stack trace via the usual {{error_type}} / {{error_message}} template fields. Works with both committed slugs and --from-file. - No
--cpu <cores> CPU cores for the ephemeral sandbox (0.1–4.0). Overrides the YAML value. Only applies with --from-file. - No
--memory <mb> Memory limit in MB for the ephemeral sandbox (128–8192). Overrides the YAML value. Only applies with --from-file. - No
--no-follow Return immediately after queueing instead of streaming logs - No
--json Print the run record as JSON when it terminates - No
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.

  1. 2d ago First seen · 43 lines · 0 tokens per session scan A 40246941e611

Subscribe to this mod's changes

workflow is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 513 tokens. 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-09-03.