speculate: Skill for Claude Code

.claude/skills/tbd/SKILL.md

tbd is a skill for Claude Code from jlevy/speculate. It costs 55 tokens per session (1,188 once invoked), scanned A, original, MIT.

A lightweight issue tracker that stores tasks and bugs in Git, the version-control system commonly used for code. It also records relationships between tasks, such as prerequisites.

In plain words
What is it for?
Use it to create, plan, update, and track issues; synchronize them; and close completed work alongside commits, pushes, and CI checks.
Why use it?
It keeps planning and task status close to the code and helps agents recover context between sessions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is jlevy/speculate's own configuration. It tells Claude Code how to work on speculate 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 speculate configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jlevy/speculate. 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/jlevy/speculate/main/.claude/skills/tbd/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jlevy/speculate

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 tbd

README.md
[![agentmods](https://agentmods.dev/badge/skills/jlevy/speculate/tbd/github.svg)](https://agentmods.dev/skills/jlevy/speculate/tbd)
Your own site
<a href="https://agentmods.dev/skills/jlevy/speculate/tbd"><img src="https://agentmods.dev/badge/skills/jlevy/speculate/tbd/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 tbd

Your own site · 80×15
<a href="https://agentmods.dev/skills/jlevy/speculate/tbd"><img src="https://agentmods.dev/badge/skills/jlevy/speculate/tbd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,188 The whole file, excluding the scripts and references it only reads on demand.
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.00055 $0.01188
Opus 5.5 $0.00022 $0.00475
Sonnet 5.5 $0.00011 $0.00238
Haiku 4.5 $0.00006 $0.00119

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

Security

Grade A, and why

tbd 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 1mo 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/skills/tbd/SKILL.md · 129 lines

How it starts

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

tbd Workflow

tbd provides lightweight, git-native task and issue tracking using beads, which are just lightweight issues managed from the CLI.

Context Recovery: Run tbd prime after compaction, clear, or new session. Hooks auto-call this in Claude Code when .tbd/ detected.

SESSION CLOSING PROTOCOL

CRITICAL: Before saying “done” or “complete”, you MUST run this checklist:

[ ] 1. Stage and commit: git add + git commit
[ ] 2. Push to remote: git push
[ ] 3. Start CI watch (BLOCKS until done): gh pr checks <PR> --watch 2>&1
[ ] 4. While CI runs: tbd close/update <id> for issues worked on
[ ] 5. While CI runs: tbd sync
[ ] 6. Return to step 3 and CONFIRM CI passed
[ ] 7. If CI failed: fix, re-push, restart from step 3

NON-NEGOTIABLE Requirements

CI: Wait for --watch to finish

The --watch flag blocks until ALL checks complete. Do NOT see “passing” in early output and move on—wait for the final summary showing all checks passed.

tbd: Update issues and sync

Every session must end with tbd in a clean state:

  • Close/update every issue you worked on
  • Run tbd sync and confirm it completed

Work is not done until pushed, CI passes, and tbd is synced.

Core Rules

  • Track all task work not being done immediately as beads using tbd (discovered work, future work, TODOs for the session, multi-session work)
  • When in doubt, prefer tbd for tracking tasks, bugs, and issues
  • Use tbd create for creating beads
  • Git workflow: update or close issues and run tbd sync at session end
  • If not given specific directions, check tbd ready for available work

Essential Commands

Finding Work

  • tbd ready - Show issues ready to work (no blockers)
  • tbd list --status open - All open issues
  • tbd list --status in_progress - Your active work
  • tbd show <id> - Detailed issue view with dependencies

Creating & Updating

  • tbd create "title" --type task|bug|feature --priority P2 - New issue
    • Priority: P0-P4 (P0=critical, P2=medium, P4=backlog). Do NOT use "high"/"medium"/"low"
  • tbd update <id> --status in_progress - Claim work
  • tbd update <id> --assignee username - Assign to someone
  • tbd close <id> - Mark complete
  • tbd close <id> --reason "explanation" - Close with reason
  • Tip: When creating multiple issues, use parallel subagents for efficiency

Read the full file on GitHub · 129 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. 1mo ago First seen · 129 lines · 55 tokens per session scan A 937d715aff91

Subscribe to this mod's changes

tbd is a skill published in the GitHub repository jlevy/speculate (34 stars, last pushed 8mo ago), licensed MIT. It adds 55 tokens to every session and 1,188 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens