agentmods.dev

block

A command that changes a task's status to blocked and records the reason in the task file. A blocked task is one that cannot proceed until a stated problem is resolved.

In plain words
What is it for?
Use it to block a task by ID, optionally selecting a project and supplying a reason, then show the impact and the steps needed to unblock it.
Why use it?
It keeps the reason for the delay visible and updates related task information, including dependent tasks that may also be affected.

Command

2 7mo ago A scan 8 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/block
Clone the repo
git clone --depth 1 https://github.com/sequenzia/claude-plugins
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 360 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.00008 $0.00360
Opus 5 $0.00004 $0.00180
Sonnet 5 $0.00002 $0.00072
Haiku 4.5 $0.00001 $0.00036

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

Security

Grade A, and why

block 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/task-manager/commands/block.md · 60 lines

What it actually says

Mark a task as blocked and document the blocking reason.

Process

  1. Parse arguments

    • Extract task ID from arguments
    • Extract reason (text after --reason)
    • Extract optional project name

  2. Locate and read the task file

    • If project name provided: Read tasks/<project>.tasks.json
    • If no project name: Find task file containing the specified task ID

  3. Validate

    • Confirm task exists
    • Warn if task is already complete or obsolete

  4. Update the task

    • Set status to "blocked"
    • Add blocking reason to notes field (append to existing notes)
    • Format: "[BLOCKED ] "

  5. Update metadata

    • Update last_updated timestamp
    • Increment version (patch bump)

  6. Write updated task file

  7. Display confirmation

Format output as:

## Task Blocked: TASK-XXX

**<title>** marked as blocked.

**Reason:** <reason>

### Impact Assessment
Tasks depending on this one:
- TASK-AAA: <title> (also now blocked)
- TASK-BBB: <title> (also now blocked)

### Resolution Needed
To unblock this task:
1. Address the blocking issue
2. Use `/spec-task-manager:complete TASK-XXX` when resolved

Or update the task with `/spec-task-manager:update` if requirements changed.

If no reason provided, prompt for one - blocking should always be documented.

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 · 60 lines · 8 tokens per session scan A ee715f19680a

Subscribe to this mod's changes

block 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 360 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.

Planning
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