An interactive setup command for configuring flow metrics for a project. It connects the project to a data source such as GitHub pull requests, Linear issues, or Git history.

Use it to detect the repository, choose a data source, define when work counts as started, and save or reconfigure the project's flow settings.

It creates the project configuration needed before collecting and interpreting work-flow data.

setup — Command by tommymorgan

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/tommymorgan/claude-plugins/setup

Clone the repo

git clone --depth 1 https://github.com/tommymorgan/claude-plugins

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

When invoked 582 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.00010	$0.00582
Opus 5	$0.00005	$0.00291
Sonnet 5	$0.00002	$0.00116
Haiku 4.5	$0.00001	$0.00058

Measured yesterday against content hash f4feafb188cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

flow/commands/setup.md · 69 lines

How it starts

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

Flow Setup

Configure flow metrics collection for the current project.

Steps

Detect git remote URL:
```
git remote get-url origin
```
If no git remote found, report: "No git remote detected. Flow metrics requires a git repository with a remote." and stop.
Generate project slug from the remote URL:
- Strip protocol (https://, git@)
- Replace / and : with -
- Strip .git suffix
- Lowercase
Check for existing config at ~/.tommymorgan/flows/<slug>.json:
- If exists, show current config and ask: "Reconfigure this project?"
Ask: "What is your data source?" Present options:
- GitHub PRs (recommended for teams using pull request workflows)
- Linear issues (for teams tracking work in Linear)
- Git history (for any repo — no external tools required)
Note: Linear and git adapters are not yet implemented. If selected, inform the user and suggest GitHub PRs for now.
Ask: "What does 'started' mean for this project?" Present source-appropriate options:
- GitHub: Earliest commit authored date on PR branch (recommended), PR opened, PR created
- Linear: Issue moved to In Progress, issue created, custom state name
- Git: First commit on branch, branch created
Ask: "What does 'finished' mean for this project?" Present source-appropriate options:
- GitHub: PR merged (recommended), PR closed
- Linear: Issue moved to Done, issue closed, custom state name
- Git: Merged to main/master, tagged
Ask source-specific connection details:
- GitHub: owner/repo (can list multiple, comma-separated). Default: infer from git remote.
- Linear: team slug or project name
- Git: main branch name (default: main)

Show summary:

Flow Configuration Summary:
- Project: <remote URL>
- Source: <source>
- Started: <boundary definition>
- Finished: <boundary definition>
- Connection: <details>

Save this configuration?

Read the full file on GitHub · 69 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.

yesterday First seen · 69 lines · 10 tokens per session scan A f4feafb188cb

Subscribe to this mod's changes

setup is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 582 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-31.

Analytics and metrics Git and workflow Productivity

setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Flow Setup

Steps

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement