tasker-to-beads

tasker-to-beads is a command for coding agents from Dowwie/tasker. It costs 0 tokens per session (558 once invoked), scanned A, original, Apache-2.0.

A command that converts Tasker task definitions into detailed Beads issues, which are trackable work items for a software project.

In plain words
What is it for?
Creating one or many Beads issues from planned Tasker tasks, including initializing Beads in the target directory when needed.
Why use it?
It carries task structure, specifications, architecture context, labels, priorities, and dependencies into the project where development happens.

Command

Part of the tasker plugin — 6 skills, 8 commands, 8 agents, 3 hooks shipped together

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/dowwie/tasker/tasker-to-beads
Clone the repo
git clone --depth 1 https://github.com/Dowwie/tasker

Or install tasker, the plugin that ships this one along with the rest of its 6 skills, 8 commands, 8 agents, 3 hooks.

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 tasker-to-beads

README.md
[![agentmods](https://agentmods.dev/badge/commands/dowwie/tasker/tasker-to-beads.svg)](https://agentmods.dev/commands/dowwie/tasker/tasker-to-beads)
Your own site
<a href="https://agentmods.dev/commands/dowwie/tasker/tasker-to-beads"><img src="https://agentmods.dev/badge/commands/dowwie/tasker/tasker-to-beads.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 558 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.00000 $0.00558
Opus 5 $0.00000 $0.00279
Sonnet 5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

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

Security

Grade A, and why

tasker-to-beads 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 5d 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.

internal/commands/tasker-to-beads.md · 72 lines

How it starts

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

Tasker to Beads

Transform Tasker task definitions into rich, self-contained Beads issues.

Use the tasker-to-beads skill: Skill("tasker-to-beads")

What This Does

  1. Asks for target directory — Where development will happen (may differ from planning project)
  2. Initializes beads in the target directory if not already done
  3. Extracts structural data from Tasker task files
  4. Uses LLM comprehension to enrich with spec context, architecture narrative, and human-readable descriptions
  5. Creates Beads issues with proper labels, priorities, and dependencies in the target project

Interactive Workflow

When invoked, this command will:

  1. First, ask: "Where would you like to create the Beads issues? This should be the directory where the actual development will take place."
    • Options: Current directory, specify path, or common locations
  2. Check if beads is initialized in that directory
  3. Initialize beads if needed (with option to customize issue prefix)
  4. Process tasks according to mode selected

Usage

  • /tasker-to-beads — Interactive mode, asks for target directory and processes all tasks
  • /tasker-to-beads T001 — Process single task by ID (still asks for target)
  • /tasker-to-beads --batch — Process all tasks and create manifest for batch import
  • /tasker-to-beads --target /path/to/project — Skip target prompt, use specified directory

CLI Commands

The tasker binary includes transform commands for mechanical transformations:

# Check status of source and target
tasker transform status -t /path/to/target

# Initialize beads in target with custom prefix
# Runs: bd init <PREFIX> && bd onboard
tasker transform init-target /path/to/target FATHOM

# Prepare context for all tasks
tasker transform context --all

# Create issue in target directory
tasker transform create T001 .tasker/beads-export/T001-enriched.json -t /path/to/target

Example Session

User: /tasker-to-beads

Claude: I'll help you transform Tasker tasks into Beads issues.

First, where would you like to create the Beads issues?
- [ ] Current directory (/Users/dev/tasker)
- [ ] Specify a different path

User: /Users/dev/fathom

Claude: Checking /Users/dev/fathom...
  - Directory exists: Yes
  - Beads initialized: No

I'll initialize Beads with prefix "FATHOM". Continue? [Y/n]

...

Read the full file on GitHub · 72 lines

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. 5d ago First seen · 72 lines · 0 tokens per session scan A c68aaf7c2ae7

Subscribe to this mod's changes

tasker-to-beads is a command published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 558 tokens. 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 commands, from other repositories

audit

Execute the canonical workflow: .agent/workflows/audit.md.

KbWen/agentic-os · 0 tokens

remediate

Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…

vyuh-labs/dxkit · 0 tokens

hf.issue

Take a rough description from the user, research the relevant codebase, and create a well-structured GitHub issue with full context, file references, and acceptance criteria.

T-rav/hydraflow · 0 tokens

migrating-fabric-trial-capacities

Migrate workspaces from trial capacity to production capacity.

data-goblin/power-bi-agentic-development · 10 tokens

orchestrate

Orchestrate a whole project (or slice) of GitHub issues into resolution-gated waves of Orca child worktrees — one autonomous worker per ticket — and babysit every PR through CI, the applicable-lens review, and third-party feedback until the human merges. Waves are resolution-gated — merged PRs, corroborated no-change…

w00fx/spec-anchored-agentic-development · 91 tokens

spec-to-tickets

Break a capability spec (or the shaping conversation that produced it, or a parent issue) into tracer-bullet tickets — vertical slices anchored on the spec's pointed stable IDs (typed, never renumbered), each declaring its blocking edges. Quizzes the human on the breakdown, then publishes to a local tickets.md or to…

w00fx/spec-anchored-agentic-development · 73 tokens