agentmods.dev

show

A task-information command that finds a task by ID in a JSON task file and displays its status, priority, description, dependencies, acceptance criteria, and source requirements.

In plain words
What is it for?
Use it to inspect a specific task, see what blocks it or what it blocks, and review the conditions required for completion.
Why use it?
It gathers a task's details and relationships in one view instead of requiring you to search task files manually.

Command

2 7mo ago A scan 7 tokens original MIT
View the source file sequenzia/claude-plugins
Install

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.

agentmods
npx agentmods add commands/sequenzia/claude-plugins/show
Clone the repo
git clone --depth 1 https://github.com/sequenzia/claude-plugins
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 432 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00432
Opus 5 $0.00003 $0.00216
Sonnet 5 $0.00001 $0.00086
Haiku 4.5 $0.00001 $0.00043

Measured yesterday against content hash 4ed16e784c85, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/mission-control/commands/show.md · 76 lines

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

  1. Locate the task file

    • Search for tasks/*.tasks.json files
    • If project-name provided, look for tasks/<project-name>.tasks.json
    • If multiple task files exist and no project specified, list them and ask user to specify

  2. Find the task

    • Parse the JSON task file
    • Search for the task by ID
    • If not found, report error and suggest similar task IDs

  3. 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"
Changes

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.

  1. yesterday First seen · 76 lines · 7 tokens per session scan A 4ed16e784c85

Subscribe to this mod's changes

show is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 432 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.

Code reviewPlanning
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens