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/sle)<a href="https://agentmods.dev/commands/tommymorgan/claude-plugins/sle"><img src="https://agentmods.dev/badge/commands/tommymorgan/claude-plugins/sle/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/sle"><img src="https://agentmods.dev/badge/commands/tommymorgan/claude-plugins/sle.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.00011 | $0.00477 |
| Opus 5.5 | $0.00004 | $0.00191 |
| Sonnet 5.5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
sle 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.
What it actually says
Flow SLE (Service Level Expectations)
Show Cycle Time percentile lines from historical flow data.
Steps
-
Resolve project config by matching git remote URL against
~/.tommymorgan/flows/- If no config: "No flow configuration found for remote URL: . Run /flow:setup to configure."
- If invalid config: "Configuration file is invalid: . Run /flow:setup to reconfigure."
-
Read flow data from
~/.tommymorgan/flows/<slug>-data.json- If no data: "No flow data found. Run /flow:fetch-data first."
-
Apply filters if provided (--author, --repo)
-
Check sample size:
- If fewer than 20 data points: "Warning: Only {count} data points available (minimum 20 recommended for reliable percentiles). Results may not be representative."
- Display results regardless (don't block)
-
Calculate percentiles at 50th, 70th, 85th, and 95th using rank-based ordering
-
Display:
Service Level Expectations ({count} items, {date_range}) {filter_description if filtered} 50th percentile: {n} days — 50% of items finish in {n} days or less 70th percentile: {n} days — 70% of items finish in {n} days or less 85th percentile: {n} days — 85% of items finish in {n} days or less 95th percentile: {n} days — 95% of items finish in {n} days or less
Arguments
--author <name>— Filter to a specific author--repo <owner/repo>— Filter to a specific repo
Important
- These are calendar days (no weekends subtracted)
- Percentiles are forecasts: "85th percentile = 12 days" means "there is an 85% chance the next item will finish in 12 days or less"
- Never communicate these as averages
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 · 47 lines · 11 tokens per session scan A df7b73dfb306
sle is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 477 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.