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/jlevy/repren/tbdnpx skills add jlevy/repren --skill tbdgit clone --depth 1 https://github.com/jlevy/reprenWhat 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.00262 | $0.06830 |
| Opus 5 | $0.00131 | $0.03415 |
| Sonnet 5 | $0.00052 | $0.01366 |
| Haiku 4.5 | $0.00026 | $0.00683 |
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 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tbd helps humans and agents ship code with greater speed, quality, and discipline.
- Beads: Git-native issue tracking (tasks, bugs, features).
Never lose work across sessions.
Drop-in replacement for
bd. - Spec-Driven Workflows: Plan features → break into beads → implement systematically.
- Knowledge Injection: 25+ engineering guidelines (TypeScript, Python, TDD, testing, Convex, monorepos) available on demand.
- Shortcuts: Reusable instruction templates for common workflows (code review, commits, PRs, cleanup, handoffs).
Installation
npm install -g get-tbd@latest # Install or upgrade the CLI (same command for both)
tbd setup --auto --prefix=<name> # Fresh project (--prefix is REQUIRED: 2-8 alphabetic chars recommended. ALWAYS ASK THE USER FOR THE PREFIX; do not guess it)
tbd setup --auto # Existing tbd project — also the upgrade step (applies any format migration; commit the diff it reports)
tbd setup --from-beads # Migration from .beads/ if `bd` has been used
If tbd refuses with “This repository requires a newer version of tbd”, run the two install/upgrade commands above.
Routine Commands
tbd --help # Command reference
tbd status # Status
tbd doctor # If there are problems
tbd setup --auto # Run any time to refresh setup
tbd prime # Restore full context on tbd after compaction
tbd web --open # Open the live, read-only bead viewer
CRITICAL: You Operate tbd, the User Doesn’t
You are the tbd operator: Users talk naturally; you translate their requests to tbd actions. DO NOT tell users to run tbd commands. That’s your job.
-
WRONG: “Run
tbd createto track this bug” -
RIGHT: (you run
tbd createyourself and tell the user it’s tracked)
Live browser requests: When the user asks to see, show, open, or view beads in a
browser, start tbd web --open yourself with the agent platform’s long-running process
facility. Do not merely print the command.
If the requested project is outside your current working directory, start
tbd web <path> --open; the path may be its repository root or any subdirectory.
Wait for the startup descriptor, give the user its loopback URL, and leave the process
running until they ask you to stop it or the session environment requires cleanup.
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 · 436 lines · 262 tokens per session scan A 41524bee6256
tbd is a skill published in the GitHub repository jlevy/repren (374 stars, last pushed 6d ago), licensed MIT. It adds 262 tokens to every session and 6,830 once invoked, about $0.0013 per session on Opus 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.
Other skills, from other repositories
ha-merge-queue
Finds open Home Assistant pull requests that are genuinely ready to merge, checking CI, the merge-gate statuses, code-owner approval, merge conflicts, requested changes and unresolved review threads. Use when looking for PRs to merge, doing merge-queue triage, or asking for "quick wins" from the open PR backlog.
setup-matt-pocock-skills
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
kanban-tui
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the ktui command is not available, but uv is available utilize uvx kanban-tui…
refactor
Refactor code to improve structure and maintainability.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.