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.
npx agentmods add commands/sequenzia/claude-plugins/show-groupgit clone --depth 1 https://github.com/sequenzia/claude-pluginsWhat 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.00008 | $0.01487 |
| Opus 5 | $0.00004 | $0.00744 |
| Sonnet 5 | $0.00002 | $0.00297 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
show-group 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 2d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show detailed information about a specific context group, including all tasks, dependencies, and progress.
Process
-
Parse arguments
$1= Group ID (required, e.g., "CG-001")$2= Project name (optional)
-
Validate arguments
- Group ID must match pattern
CG-XXX - If invalid, show usage help
- Group ID must match pattern
-
Locate and read the task file
- If project name provided: Read
tasks/$2.tasks.json - If no project name: Find most recently modified
.tasks.json
- If project name provided: Read
-
Find the requested context group
- Search
context_groupsarray for matching ID - If not found, list available groups
- Search
-
Gather task details
- For each task in the group, collect full task information
- Calculate completion status
- Identify dependencies within and outside the group
-
Display group details
Format output as:
## Context Group: CG-001
**Status:** active
**Estimated Tokens:** 72,000 / 80,000 effective limit
**Phases Covered:** 1, 2
### Progress
- **Completed:** 2 of 5 tasks (40%)
- **In Progress:** 1 task
- **Blocked:** 0 tasks
- **Not Started:** 2 tasks
---
### Tasks
#### TASK-001: Initialize project structure [COMPLETE]
- **Priority:** high | **Complexity:** S | **Tokens:** 1,700
- **Description:** Set up the base project directory structure and configuration files
- **Acceptance Criteria:**
- [x] Directory structure created
- [x] package.json configured
- [x] TypeScript config in place
---
#### TASK-002: Setup database schema [COMPLETE]
- **Priority:** high | **Complexity:** M | **Tokens:** 4,200
- **Dependencies:** TASK-001 (complete)
- **Description:** Define database tables and relationships
- **Acceptance Criteria:**
- [x] User table created
- [x] Session table created
- [x] Migrations written
---
#### TASK-003: Implement user model [IN PROGRESS]
- **Priority:** high | **Complexity:** M | **Tokens:** 4,200
- **Dependencies:** TASK-002 (complete)
- **Description:** Create the User model with CRUD operations
- **Acceptance Criteria:**
- [ ] User class implemented
- [ ] Validation logic added
- [ ] Unit tests passing
---
#### TASK-004: Create authentication service [NOT STARTED]
- **Priority:** critical | **Complexity:** L | **Tokens:** 10,200
- **Dependencies:** TASK-003 (in progress)
- **Blocked By:** TASK-003
- **Description:** Implement authentication logic with JWT
- **Acceptance Criteria:**
- [ ] Login endpoint working
- [ ] Token generation implemented
- [ ] Token validation middleware
---
#### TASK-005: Add password hashing [NOT STARTED]
- **Priority:** high | **Complexity:** S | **Tokens:** 1,700
- **Dependencies:** TASK-001 (complete)
- **Description:** Implement secure password hashing utility
- **Acceptance Criteria:**
- [ ] bcrypt integration
- [ ] Hash and verify functions
- [ ] Salt rounds configurable
---
### Dependency Graph (This Group)
TASK-001 (complete) ├── TASK-002 (complete) │ └── TASK-003 (in_progress) │ └── TASK-004 (blocked) └── TASK-005 (not_started)
### External Dependencies
- **From Previous Groups:** None
- **For Next Groups:**
- CG-002 depends on: TASK-003, TASK-004
### Token Breakdown
| Task | Base | Overhead | Total |
|------|------|----------|-------|
| TASK-001 | 1,500 | 200 | 1,700 |
| TASK-002 | 4,000 | 200 | 4,200 |
| TASK-003 | 4,000 | 200 | 4,200 |
| TASK-004 | 10,000 | 200 | 10,200 |
| TASK-005 | 1,500 | 200 | 1,700 |
| **Total** | | | **22,000** |
---
### Ready to Start Now
Tasks with all dependencies satisfied:
- **TASK-005:** Add password hashing (high, S)
### Blocked Tasks
- **TASK-004:** Waiting on TASK-003
---
**Commands:**
- Mark complete: `/task-manager:complete TASK-XXX`
- Update task: `/task-manager:update TASK-XXX --status in_progress`
- See all groups: `/task-manager:status`
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.
- 2d ago First seen · 226 lines · 8 tokens per session scan A 9f7945625327
show-group is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 1,487 once invoked, about $0.0000 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).