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 skills/kastheco/claude-plugins/task-workflownpx skills add kastheco/claude-plugins --skill task-workflowgit clone --depth 1 https://github.com/kastheco/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.00075 | $0.00904 |
| Opus 5 | $0.00037 | $0.00452 |
| Sonnet 5 | $0.00015 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
ClickUp Task Workflow 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClickUp Task Workflow
Overview
This skill provides workflow patterns for managing ClickUp tasks integrated with kas workflow commands. The core principle: delegate all ClickUp API calls to the clickup-task-agent to keep the main conversation context clean.
Core Principle
NEVER call ClickUp MCP tools directly in main context.
All ClickUp operations delegate to the clickup-task-agent subagent which returns concise summaries. This prevents verbose API responses from polluting the conversation.
Command Mapping
| /task Command | Skills/Commands Used | ClickUp Actions |
|---|---|---|
/task:start CU-xxx |
superpowers:brainstorming → kas:review-plan (loop) → superpowers:subagent-driven-development OR superpowers:executing-plans |
Fetch task, set "in progress", assign |
/task:done |
/kas:verify → /kas:done → PR |
Set "ready for review", comment PR |
/task:merge |
/kas:merge |
Set "complete" |
/task:status [id] |
None | Fetch and display status |
/task:new |
None | Create task via interview |
Planning Workflow
/task:start uses superpowers-driven planning:
- Fetch task via clickup-task-agent (capture original status for rollback)
- Enter plan mode using EnterPlanMode tool
- Brainstorming via
superpowers:brainstorming- explores, asks questions, outputs design - Review loop via
kas:review-plan- max 5 iterations until APPROVED or user overrides/aborts - Implementation via user choice:
- Option 1:
superpowers:subagent-driven-development(same session) - Option 2:
superpowers:executing-plans(separate session with worktree)
- Option 1:
Detection Triggers
Activate this skill when detecting:
Task References
- URLs:
https://app.clickup.com/t/... - Task IDs:
CU-xxx,#xxx,task xxx - Work phrases: "work on", "implement", "fix task", "start on"
Task Creation
- Creation phrases: "create task", "new feature", "log bug", "file issue"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 93 lines · 75 tokens per session scan A 088089202a9f
ClickUp Task Workflow is a skill published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 904 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…