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.
git clone --depth 1 https://github.com/tommymorgan/claude-pluginsWrote 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.
[](https://agentmods.dev/commands/tommymorgan/claude-plugins/setup)<a href="https://agentmods.dev/commands/tommymorgan/claude-plugins/setup"><img src="https://agentmods.dev/badge/commands/tommymorgan/claude-plugins/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/tommymorgan/claude-plugins/setup"><img src="https://agentmods.dev/badge/commands/tommymorgan/claude-plugins/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00010 | $0.00582 |
| Opus 5.5 | $0.00004 | $0.00233 |
| Sonnet 5.5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
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 1mo 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 — 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 originIf 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
.gitsuffix - 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?
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.
- 1mo ago First seen · 69 lines · 10 tokens per session scan A f4feafb188cb
setup is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 582 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.