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.
git clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWrote 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.
[](https://agentmods.dev/commands/dgalarza/claude-code-workflows/linear-worktree)<a href="https://agentmods.dev/commands/dgalarza/claude-code-workflows/linear-worktree"><img src="https://agentmods.dev/badge/commands/dgalarza/claude-code-workflows/linear-worktree/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.
<a href="https://agentmods.dev/commands/dgalarza/claude-code-workflows/linear-worktree"><img src="https://agentmods.dev/badge/commands/dgalarza/claude-code-workflows/linear-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00905 |
| Opus 5.5 | $0.00000 | $0.00362 |
| Sonnet 5.5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
linear-worktree 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Issue Worktree Setup
Set up a new git worktree for a Linear issue, creating a separate working directory off the main branch.
Usage
/linear-worktree <project-path> <linear-issue-id>
What this command does
- Fetch Linear Issue: Retrieves issue details to get the suggested git branch name
- Create Worktree: Creates a new git worktree in
../tracewell-<branch-name>directory - Switch Context: Changes to the new worktree directory
- Ready for Work: Leaves you in the new worktree, ready to run
/linear-implement
Arguments
- First argument: Path to the project directory (e.g.,
tracewell2) - Second argument: The Linear issue ID (e.g.,
TRA-9,DEV-123)
Requirements
- Linear integration configured (MCP Linear tools available)
- Current working directory must be a git repository
mainbranch exists and is up-to-date
Example
/linear-worktree tracewell2 TRA-9
This will:
- Change to the
tracewell2directory - Fetch Linear issue TRA-9 details
- Create a new worktree at
../tracewell-<branch-name> - Copy
.envandconfig/master.keyto the new worktree - Switch to the new worktree directory
- Run
bin/setupinside the new worktree - Ready for you to run
/linear-implement TRA-9
Benefits of Using Worktrees
- Work on multiple features simultaneously without branch switching
- Keep your main working directory clean
- Avoid stashing changes when switching between issues
- Each worktree maintains its own file state
I'll help you set up a new git worktree for the Linear issue. Let me start by parsing the arguments and changing to the project directory.
Step 1: Navigate to Project Directory
First, I'll change to the specified project directory:
Project path: {first argument} Issue ID: {second argument}
Step 2: Fetch Linear Issue Details
I'll retrieve the issue information to get the suggested git branch name:
Let me fetch the complete issue details to determine the proper branch name for the worktree.
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.
- 1mo ago First seen · 125 lines · 0 tokens per session scan A b3fe6f023f63
linear-worktree is a command published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 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-30.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.