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 skills/jpm1118/threadwork/using-threadworknpx skills add JPM1118/Threadwork --skill using-threadworkgit 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.01937 |
| Opus 5 | $0.00000 | $0.00968 |
| Sonnet 5 | $0.00000 | $0.00387 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
using-threadwork 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Threadwork (Meta-Skill)
Establish mandatory workflow for consistently discovering and applying relevant skills before any action.
Core Principle
IF A SKILL FOR THE TASK EXISTS, YOU MUST USE IT OR YOU WILL FAIL
This is not optional. This is not a suggestion. Skills exist because agents fail without them.
When to Use This Skill
ALWAYS. This skill applies to every action you take in a Threadwork-enabled project.
Before doing ANYTHING, check if a skill applies.
The Pre-Action Protocol
Before every significant action, execute this checklist:
┌─────────────────────────────────────────────────────────────┐
│ Pre-Action Protocol Checklist │
├─────────────────────────────────────────────────────────────┤
│ │
│ □ 1. IDENTIFY what I'm about to do │
│ │
│ □ 2. CHECK if a skill exists for this action │
│ │
│ □ 3. READ the skill (current version, not memory) │
│ │
│ □ 4. ANNOUNCE which skill I'm using │
│ │
│ □ 5. FOLLOW the skill exactly │
│ │
└─────────────────────────────────────────────────────────────┘
Available Skills Reference
Workflow Skills (When to use each)
| Task | Skill to Use |
|---|---|
| Exploring a problem | brainstorming |
| Setting up feature branch | worktree-setup |
| Creating implementation plan | beads-backed-planning |
| Executing a single task | beads-tdd-execution |
| Running multiple tasks | executing-plans |
| Using subagents for tasks | subagent-driven-development |
| Landing completed work | finishing |
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 · 266 lines · 0 tokens per session scan A abf510151fb7
using-threadwork is a skill 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,937 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…