agentmods.dev

continue-task

A command for resuming a software task that was left in progress. It finds the current task, shows its details and plan, and continues the remaining implementation work.

In plain words
What is it for?
Use it when work has stopped partway through a task and you need to inspect its status, continue the plan, finish the implementation, and mark it done.
Why use it?
It avoids losing track of unfinished tasks, their priorities, existing plans, and required follow-up records.

Command

19 4d ago A scan 11 tokens original MIT
View the source file smekai/taskplanner
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/smekai/taskplanner/continue-task
Clone the repo
git clone --depth 1 https://github.com/smekai/taskplanner
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 386 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.00011 $0.00386
Opus 5 $0.00005 $0.00193
Sonnet 5 $0.00002 $0.00077
Haiku 4.5 $0.00001 $0.00039

Measured 2d ago against content hash 0065211502fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

continue-task 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.

plugins/taskplanner/commands/continue-task.md · 38 lines

What it actually says

Continue Task

Resume implementation of a task that is already in progress.

Steps

Determine the absolute current repository root first and pass it as workspace_root on every MCP call.

  1. Call taskplanner_list with state: "In Progress" to find current tasks.
  2. If no tasks are in progress, tell the user and suggest using /next-task instead.
  3. If exactly one task is in progress, proceed with that task.
  4. If multiple tasks are in progress, show them all and ask the user which one to continue.
  5. Call taskplanner_get with the selected task ID to retrieve full details including the existing plan.
  6. Present the task details to the user:
    • Task ID and title
    • Priority and tags
    • Description
    • Existing plan (if any)
  7. Continue implementing the task from where it was left off: a. If there is an existing ### Plan, follow it — check off completed steps and continue with the next ones. b. If there is no plan and .tasks/config.json has aiPlanRequired: true, write the plan first. c. Implement the remaining work. d. When done, call taskplanner_move to move the task to "Done". e. Update the ### Plan to a short done-summary. f. Append a short entry to .tasks/WORK_LOG.md if that file exists (newest at top). g. Add a CHANGELOG.md entry under ## [Unreleased].

Conventions

  • Do NOT change task IDs.
  • Keep the --- separator between tasks in markdown files.
  • Refer to .tasks/config.json and CLAUDE.md for project-specific conventions.
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. 2d ago First seen · 38 lines · 11 tokens per session scan A 0065211502fd

Subscribe to this mod's changes

continue-task is a command published in the GitHub repository smekai/taskplanner (19 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 386 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-30.

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