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/sequenzia/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/sequenzia/claude-plugins/show)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/show"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/show/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/sequenzia/claude-plugins/show"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/show.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.00007 | $0.00432 |
| Opus 5.5 | $0.00003 | $0.00173 |
| Sonnet 5.5 | $0.00001 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
show 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
Display comprehensive details for a specific task.
Arguments:
task-id(required): The task ID to display (e.g., TASK-001)project-name(optional): Project name to narrow search if multiple task files exist
Process
-
Locate the task file
- Search for
tasks/*.tasks.jsonfiles - If
project-nameprovided, look fortasks/<project-name>.tasks.json - If multiple task files exist and no project specified, list them and ask user to specify
- Search for
-
Find the task
- Parse the JSON task file
- Search for the task by ID
- If not found, report error and suggest similar task IDs
-
Display task details
Output Format
## TASK-XXX: <title>
**Status:** <status>
**Priority:** <priority>
**Complexity:** <complexity>
### Description
<full description>
### Dependencies
**Depends on:**
- TASK-YYY: <title> [<status>]
- TASK-ZZZ: <title> [<status>]
**Blocked by (incomplete):**
- TASK-YYY: <title>
**Blocks:**
- TASK-AAA: <title>
- TASK-BBB: <title>
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
### Source Requirements
- Section 5.1: Feature Name
- US-001: User story reference
### Notes
<any additional notes>
---
**Ready to start:** Yes/No
**Execution phase:** <phase number>
Edge Cases
- If task is blocked, highlight the blocking tasks prominently
- If task is complete, show checkmarks on acceptance criteria
- If task has no dependencies, note "No dependencies"
- If task blocks nothing, note "Does not block other tasks"
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 · 76 lines · 7 tokens per session scan A 4ed16e784c85
show is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 432 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.