A task-sizing guide that chooses between one context, delegated subagents, or a workflow. A subagent is a separate AI worker, while a workflow is a repeatable process for larger or recurring work.

It is for deciding how to divide work and giving a one-line reason for the choice.

It removes guesswork about how to run a task and checks whether workflows are available before recommending one.

assess — Skill for Claude Code by melodic-software/claude-code-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.

Any agent

npx skills add melodic-software/claude-code-plugins --skill assess

Clone the repo

git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

Made for: Claude Code.

Or install multi-agent, the plugin that ships this one along with the rest of its 3 skills, 2 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/assess/github.svg)](https://agentmods.dev/skills/melodic-software/claude-code-plugins/assess)

Your own site

<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/assess"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/assess/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/assess"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/assess.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 933 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00113	$0.00933
Opus 5.5	$0.00045	$0.00373
Sonnet 5.5	$0.00023	$0.00187
Haiku 4.5	$0.00011	$0.00093

Measured 13d ago against content hash c4b9b5652717, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

assess 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 13d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/workflow-availability.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/multi-agent/skills/assess/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

One verdict for one task: workflow, subagent or single, with a one-line reason. A skill that is about to launch a workflow, or a person deciding how to run a large task, asks here instead of restating the rule.

The rule

Our decision: a workflow only when the work outgrows one context or repeats the same steps over many independent items, so that holding the loop in a script beats holding it in a conversation. A subagent when a few delegated tasks fit the turn, or when the work is one dependent chain that still needs a fresh context. Single when the task fits this context and is one dependent chain.

The comparison this rule rests on lives upstream; read it there when a case is close rather than recalling it:

Pointer: https://code.claude.com/docs/en/workflows#when-to-use-a-workflow
As of: 2026-10-02
Recheck: the page changes its comparison of subagents, skills, agent teams and workflows, or adds a scale or interruption row.

Steps

Availability. Run:
```
${CLAUDE_SKILL_DIR}/scripts/workflow-availability.sh
```
It reads the off switches the script knows and prints verdict off or verdict not-off. Then look at the tools you can call right now: workflows are available only when the verdict is not-off and Workflow is one of them. A name in a grant or in this text does not count. The tool's absence covers every switch the script cannot see. Where the switches are documented: https://code.claude.com/docs/en/workflows#turn-workflows-off (as of 2026-10-02; recheck when a new switch appears there). Done when you can say available or name the switch or the missing tool.
Size the task. Name the item count or the context it needs, and whether the steps depend on each other. Read only what you need to count. Done when you have a number or a context estimate and a dependency shape.
Verdict. Apply the rule. When workflows are unavailable, workflow becomes subagent, and the reason names the switch or the missing tool. Done when the two output lines are written.

Read the full file on GitHub · 87 lines

Files

What ships with it

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

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.

13d ago First seen · 87 lines · 113 tokens per session scan A c4b9b5652717

Subscribe to this mod's changes

assess is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 933 once invoked, about $0.0005 per session on Opus 5.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-10-03.

Building agents Claude Code Planning agents ai-tools marketplace mcp plugins

parallel-orchestrator

Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…

jimmc414/claude-code-plugin-marketplace · 78 tokens

parallel-worker

Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.

jimmc414/claude-code-plugin-marketplace · 59 tokens

assess