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/completegit 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.00011 | $0.00575 |
| Opus 5 | $0.00005 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
complete 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mark a task as complete and update all dependent task relationships.
Arguments:
task-id(required): The task ID to mark complete (e.g., TASK-001)project-name(optional): Project name if multiple task files exist
Process
-
Locate and validate
- Find the task file (
tasks/*.tasks.jsonortasks/<project-name>.tasks.json) - Verify the task exists
- Check current status (warn if already complete)
- Find the task file (
-
Update task status
- Set
statusto "complete" - Update
metadata.last_updatedtimestamp - Recalculate
metadata.completion_percentage
- Set
-
Update dependent tasks
- For each task that has this task in
blocked_by:- Remove this task from their
blocked_byarray - If
blocked_bybecomes empty and status was "blocked", change to "not_started"
- Remove this task from their
- Track which tasks became unblocked
- For each task that has this task in
-
Write updated file
- Save the modified JSON to the task file
- Preserve formatting
-
Display results
Output Format
## Task Completed
**TASK-XXX:** <title>
Status: not_started -> complete
### Progress Update
- Completion: 45% -> 50% (10/20 tasks)
- Tasks unblocked: 2
### Newly Unblocked Tasks
The following tasks can now be started:
1. **TASK-AAA:** <title>
- Priority: high
- Complexity: M
- Was waiting on: TASK-XXX
2. **TASK-BBB:** <title>
- Priority: medium
- Complexity: S
- Was waiting on: TASK-XXX, TASK-YYY (TASK-YYY already complete)
### Recommended Next
Based on priority and dependencies:
1. **TASK-AAA** - High priority, medium complexity
2. **TASK-CCC** - High priority, small complexity
Run `/mission-control:next` for full recommendations.
Edge Cases
- Task already complete: Warn but don't error
- Task is blocked: Error - cannot complete a blocked task without completing blockers first
- Task in progress: Allow completion (normal flow)
- No tasks unblocked: Note that no new tasks were unblocked
- All tasks complete: Congratulate user on completing the project!
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.
- yesterday First seen · 88 lines · 11 tokens per session scan A 4c057d94b6e0
complete is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 575 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.