Threadwork: Instructions file for Claude Code

CLAUDE.md

Threadwork CLAUDE.md is an instructions file for Claude Code from JPM1118/Threadwork. It costs 878 tokens per session, scanned A, original, MIT.

Instructions for Threadwork, a Claude Code plugin for structured development workflows, persistent memory, and issue tracking. It describes the plugin's Markdown skills, commands, hooks, configuration, and tests.

In plain words
What is it for?
Use it when editing Threadwork commands, skills, session hooks, configuration schemas, examples, or tests, and when running its static validation script.
Why use it?
It gives the coding agent the repository's workflow and testing rules so changes fit the plugin's structure and can be checked consistently.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is JPM1118/Threadwork's own configuration. It tells Claude Code how to work on Threadwork itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Threadwork configures →

Reuse

Borrowing it

Nothing to install: this file belongs to JPM1118/Threadwork. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JPM1118/Threadwork/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/JPM1118/Threadwork

Made for: Claude Code.

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 Threadwork CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jpm1118/threadwork/claude-md/github.svg)](https://agentmods.dev/instructions/jpm1118/threadwork/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jpm1118/threadwork/claude-md"><img src="https://agentmods.dev/badge/instructions/jpm1118/threadwork/claude-md/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 Threadwork CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jpm1118/threadwork/claude-md"><img src="https://agentmods.dev/badge/instructions/jpm1118/threadwork/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 878 This file is loaded in full into every session.
When invoked 878 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00878 $0.00878
Opus 5.5 $0.00351 $0.00351
Sonnet 5.5 $0.00176 $0.00176
Haiku 4.5 $0.00088 $0.00088

Measured 2mo ago against content hash 4a7dcba7508a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Threadwork CLAUDE.md 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 2mo 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.

CLAUDE.md · 91 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

Threadwork is a Claude Code plugin for structured development workflows with persistent memory. It combines workflow orchestration patterns from Superpowers with persistent issue tracking from Beads.

Type: Claude Code plugin (pure Markdown skills/commands + configuration files) No build process - the plugin is ready to use as-is

Testing

# Run static validation tests (validates JSON/YAML configs, skill files exist, hook outputs)
./tests/run-static-tests.sh

The tests validate: plugin manifest, hook JSON output, all 20 SKILL.md files, schema validity, and example configuration.

Pressure testing and E2E tests are manual - see tests/TESTING_STRATEGY.md for procedures.

Architecture

Plugin Structure

commands/           User-facing commands (/init, /finish-and-close)
skills/             20 reusable workflow skills (Markdown instructions)
hooks/              Session lifecycle hooks (session-start.sh)
schemas/            JSON Schema for .threadwork.yaml validation
examples/           Example configuration

Core Workflow

The plugin implements this lifecycle:

  1. /init - Create .threadwork.yaml, initialize Beads on beads-metadata branch
  2. brainstorming skill - Explore problem space
  3. worktree-setup skill - Create git worktree for isolated development
  4. beads-backed-planning skill - Create epic + tasks in Beads
  5. beads-tdd-execution skill - Implement each task (RED-GREEN-REFACTOR)
  6. verification-before-completion skill - Require evidence before claiming done
  7. code-review skill - Quality gate between tasks
  8. finishing skill - Assess readiness, determine landing strategy
  9. /finish-and-close - Merge/PR and cleanup

Key Architectural Principles

  1. Beads is source of truth - Persistent task tracking survives conversation compaction
  2. Linear task dependencies - bd ready always returns exactly one next task
  3. TDD enforced - RED (failing test) before GREEN (implementation), always
  4. Subagents never create issues - They report discoveries; orchestrator decides
  5. Always use bd --no-daemon - Avoids worktree path confusion
  6. Skill-invokes-command pattern - Skills handle judgment; commands handle deterministic execution
  7. One Beads issue per task - Tasks contain multiple TDD steps in their design field

Read the full file on GitHub · 91 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. 2mo ago First seen · 91 lines · 878 tokens per session scan A 4a7dcba7508a

Subscribe to this mod's changes

Threadwork CLAUDE.md is an instructions file published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 10mo ago), licensed MIT. It adds 878 tokens to every session, about $0.0035 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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens