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/status)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/status"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/status/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/status"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/status.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.00683 |
| Opus 5.5 | $0.00003 | $0.00273 |
| Sonnet 5.5 | $0.00001 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
status 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Display a summary of task progress and completion status.
Arguments:
project-name(optional): Project name to show status for specific task file
Process
-
Locate task files
- Search for
tasks/*.tasks.jsonfiles - If
project-nameprovided, usetasks/<project-name>.tasks.json - If multiple files and no project specified, show status for all or ask user
- Search for
-
Calculate metrics
- Count tasks by status (not_started, in_progress, blocked, complete)
- Calculate completion percentage
- Identify ready tasks (not_started with empty blocked_by)
- Count tasks per execution phase
-
Display summary
Output Format
# Task Status: <project-name>
**Source:** <spec-document>
**Last Updated:** <timestamp>
## Progress
| Metric | Value |
|--------|-------|
| Total Tasks | XX |
| Completed | XX (XX%) |
| In Progress | XX |
| Blocked | XX |
| Not Started | XX |
## Completion Bar
[████████░░░░░░░░░░░░] 40% Complete
## By Priority
| Priority | Total | Done | Remaining |
|----------|-------|------|-----------|
| Critical | X | Y | Z |
| High | X | Y | Z |
| Medium | X | Y | Z |
| Low | X | Y | Z |
## By Complexity
| Size | Total | Done | Remaining |
|------|-------|------|-----------|
| XS | X | Y | Z |
| S | X | Y | Z |
| M | X | Y | Z |
| L | X | Y | Z |
| XL | X | Y | Z |
## Execution Phases
| Phase | Name | Tasks | Done |
|-------|------|-------|------|
| 1 | Foundation | 5 | 3/5 |
| 2 | Core Features | 8 | 0/8 |
| 3 | Polish | 4 | 0/4 |
## Ready to Start
Tasks with no blockers (can begin now):
1. **TASK-XXX:** <title> (priority: high, complexity: M)
2. **TASK-YYY:** <title> (priority: medium, complexity: S)
## Currently Blocked
Tasks waiting on dependencies:
1. **TASK-AAA:** Blocked by TASK-XXX, TASK-YYY
2. **TASK-BBB:** Blocked by TASK-ZZZ
## Quick Actions
- View task: `/mission-control:show TASK-XXX`
- Complete task: `/mission-control:complete TASK-XXX`
- Next recommendations: `/mission-control:next`
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 · 111 lines · 7 tokens per session scan A 7bba482ee5c5
status 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 683 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.