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 commands/jpm1118/threadwork/initgit clone --depth 1 https://github.com/JPM1118/ThreadworkWhat 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.00000 | $0.01498 |
| Opus 5 | $0.00000 | $0.00749 |
| Sonnet 5 | $0.00000 | $0.00300 |
| Haiku 4.5 | $0.00000 | $0.00150 |
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.
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:
- You are in a git repository
- The Beads CLI (
bd) is installed:npm install -g @anthropic/beads
What This Command Does
- Detects project state - Examines git branches, existing Beads setup, and any prior Threadwork configuration
- Proposes configuration - Suggests defaults based on detected patterns
- Asks for confirmation - Single confirmation point (not question-by-question)
- Creates configuration - Writes
.threadwork.yamlwith confirmed settings - Initializes Beads - Runs
bd init --branch beads-metadataif 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
devbranch exists → proposebase_branch: dev - Else if
developbranch exists → proposebase_branch: develop - Else if
mainbranch exists → proposebase_branch: main - Else → propose
base_branch: main(will be created)
Branch Prefix Detection:
- Look for existing
feature/*branches → proposebranch_prefix: feature/ - Look for existing
feat/*branches → proposebranch_prefix: feat/ - Otherwise → propose
branch_prefix: feature/
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.
- yesterday First seen · 225 lines · 0 tokens per session scan A 40c38a10c18a
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.