tasks

tasks is a skill for Claude Code, Codex from get-bb/bb. It costs 20 tokens per session (1,392 once invoked), scanned A, original, MIT.

A guide for using the Tasks plugin to manage tracked work. It explains how to inspect task records, choose a worker setup, delegate work, and report results.

In plain words
What is it for?
Use it when working from a task key, reading task details, creating delegation presets, assigning work, or adding progress and outcome updates.
Why use it?
It keeps task details, comments, attachments, delegated work, and status updates in one record instead of leaving them scattered.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when working from a task key, reading task details, creating delegation presets, assigning work, or adding progress and outcome updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/get-bb/bb/tasks
About the project

bb is an agentic IDE that lets users control, customize, and automate a software-development environment through a desktop app, web app, command-line interface, or HTTP API. Developers use it to run work in observable threads that can be steered or handed off to other agents. Its catalogue add-ons provide skills and instructions for working with bb.

get-bb/bb · 4,324 stars · on GitHub · getbb.app

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 get-bb/bb --skill tasks
Clone the repo
git clone --depth 1 https://github.com/get-bb/bb

Made for: Claude Code, Codex.

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.

agentmods badge for tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/get-bb/bb/tasks/github.svg)](https://agentmods.dev/skills/get-bb/bb/tasks)
Your own site
<a href="https://agentmods.dev/skills/get-bb/bb/tasks"><img src="https://agentmods.dev/badge/skills/get-bb/bb/tasks/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.

agentmods 80×15 button for tasks

Your own site · 80×15
<a href="https://agentmods.dev/skills/get-bb/bb/tasks"><img src="https://agentmods.dev/badge/skills/get-bb/bb/tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,392 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00020 $0.01392
Opus 5.5 $0.00008 $0.00557
Sonnet 5.5 $0.00004 $0.00278
Haiku 4.5 $0.00002 $0.00139

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

Security

Grade A, and why

tasks 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/tasks/skills/tasks/SKILL.md · 146 lines

How it starts

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

Tasks

Use the bb tasks CLI to understand the assigned task, keep its record useful, and report the outcome where the work is tracked.

For task dispatch and execution presets, read references/delegation.md.

Work a task

  1. Find and read the task before acting:

    bb tasks show ABC-12
    

    The detail includes the description, status, priority, labels, subtasks, comments, attachments, attached worker threads, and the GitHub pull requests those threads produced (from environment metadata, with state open/draft/merged/closed). Use bb tasks show ABC-12 --json when the result will drive commands or code.

    For project-wide discovery, bb tasks list returns at most 100 rows by default. Pass --limit 1-500; in JSON, continue with nextCursor via the same filters/sort and --cursor <value> (human output prints the exact continuation option). A task-list mutation makes an old cursor stale, so restart without it.

  2. Fetch every relevant attachment before making assumptions about it:

    bb tasks attachment get <attachment-id> --out <path>
    
  3. Do the work. Post one substantive comment at each meaningful milestone, such as a completed investigation, an implementation ready for validation, or a concrete blocker:

    bb tasks comment ABC-12 --body "Implemented the change; focused validation now passes."
    

    Add --notify only when the new comment should be delivered to the thread that authored the task's most recent agent reply. This resumes an idle recipient; with no prior agent reply, the comment is recorded without targeting an unrelated thread. In agent context, the new comment keeps the current thread identity and an explicit --author, while delivery still targets the prior latest responder rather than the new comment itself.

  4. Attach result artifacts that belong with the task, such as reports, screenshots, patches, or generated files:

Read the full file on GitHub · 146 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.

  1. yesterday Changed · +2 lines c02eef5b2512
  2. 14d ago Changed · +4 lines 175c3918d7fe
  3. 27d ago Changed · +15 lines 7e453e77863e
  4. 1mo ago Changed · -12 lines · -26 tokens per session 272a3870f60a
  5. 1mo ago First seen · 137 lines · 46 tokens per session scan A f6ca58a82d1d

Subscribe to this mod's changes

tasks is a skill published in the GitHub repository get-bb/bb (4,324 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,392 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

using-grove

Use when orchestrating Grove workspaces from outside, including creating or supervising host or container agents, steering a fleet, using Grove CLI or MCP tools, or having agents write to each other through the mailbox. Also use when splitting work across workspaces, reviewing a diff from several angles, managing…

bearlike/Grove · 92 tokens

working-in-grove

Use when working inside a Grove workspace, including reporting task phase, updating a workspace or its ticket links, using GROVEPHASEFILE, writing to another Grove agent through the mailbox, or waiting on slow work like CI by registering a watch instead of sleeping. Also use when a worktree has a phase file, when…

bearlike/Grove · 100 tokens

leading-in-grove

Use when you lead a fleet of Grove teammates toward one deliverable, including deciding how many to spawn and how to split the work, writing their onboarding prompt, getting acknowledgment, running scheduled check-ins, answering their mailbox questions, keeping tickets and your own status compaction-proof, reviewing…

bearlike/Grove · 118 tokens

cradle-cli

Use whenever you need to read, inspect, wait on, or mutate Cradle-owned state or workflows, including issues, delegation, sessions, awaits, CI/review waits, timed waits, Work inspection, workspaces and git inspection, Chronicle, automations, usage, observability, skills, agents, profiles, providers, preferences…

wibus-wee/cradle-app · 152 tokens

setup

Create a project wiki with a useful Home, starter pages, and a writing guide.

nimbalyst/nimbalyst · 19 tokens

update

Write and maintain project wiki pages, decisions, and links. Use for any wiki page, including architecture or product maps, diagrams, HTML pages and other visuals, and before changing code a page covers.

nimbalyst/nimbalyst · 42 tokens