init

A project setup command for Threadwork that detects the current Git repository and proposes configuration before creating it. Git is the version-control system used to track code changes.

In plain words
What is it for?
Use it in an existing Git repository to create `.threadwork.yaml` and initialize Beads when that setup is missing. Beads is the required command-line task-tracking tool.
Why use it?
It removes the need to inspect the project and create the initial configuration by hand.

Command

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/jpm1118/threadwork/init
Clone the repo
git clone --depth 1 https://github.com/JPM1118/Threadwork
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 1,498 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.01498
Opus 5 $0.00000 $0.00749
Sonnet 5 $0.00000 $0.00300
Haiku 4.5 $0.00000 $0.00150

Measured yesterday against content hash 40c38a10c18a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/init.md · 225 lines

How it starts

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

/init - Initialize Threadwork for a Project

Initialize Threadwork in the current project. This command detects your project's existing configuration and proposes sensible defaults.

Prerequisites

Before running this command, ensure:

  1. You are in a git repository
  2. The Beads CLI (bd) is installed: npm install -g @anthropic/beads

What This Command Does

  1. Detects project state - Examines git branches, existing Beads setup, and any prior Threadwork configuration
  2. Proposes configuration - Suggests defaults based on detected patterns
  3. Asks for confirmation - Single confirmation point (not question-by-question)
  4. Creates configuration - Writes .threadwork.yaml with confirmed settings
  5. Initializes Beads - Runs bd init --branch beads-metadata if Beads not already initialized

Execution Steps

Step 1: Check Prerequisites

Run these commands to verify prerequisites:

# Check if we're in a git repo
git rev-parse --is-inside-work-tree

# Check if Beads CLI is installed
bd --version

If bd is not found, stop and inform the user:

Error: Beads CLI (bd) not found. Install with: npm install -g @anthropic/beads

Step 2: Detect Project State

Run these commands to understand the current state:

# List all branches (local and remote)
git branch -a

# Check if .threadwork.yaml exists
test -f .threadwork.yaml && echo "exists" || echo "not found"

# Check if Beads is initialized (look for .beads directory or bd status)
bd --no-daemon status 2>/dev/null || echo "beads not initialized"

Step 3: Analyze and Propose Configuration

Based on detection results, determine:

Base Branch Detection:

  • If dev branch exists → propose base_branch: dev
  • Else if develop branch exists → propose base_branch: develop
  • Else if main branch exists → propose base_branch: main
  • Else → propose base_branch: main (will be created)

Branch Prefix Detection:

  • Look for existing feature/* branches → propose branch_prefix: feature/
  • Look for existing feat/* branches → propose branch_prefix: feat/
  • Otherwise → propose branch_prefix: feature/

Read the full file on GitHub · 225 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. yesterday First seen · 225 lines · 0 tokens per session scan A 40c38a10c18a

Subscribe to this mod's changes

init is a command published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,498 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-31.