Borrowing it
Nothing to install: this file belongs to seasonedcc/discord-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/seasonedcc/discord-manager/main/.claude/skills/worktrees/SKILL.mdgit clone --depth 1 https://github.com/seasonedcc/discord-managerWrote 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/skills/seasonedcc/discord-manager/worktrees)<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/worktrees"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/worktrees/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/skills/seasonedcc/discord-manager/worktrees"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/worktrees.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.00065 | $0.01147 |
| Opus 5 | $0.00032 | $0.00574 |
| Sonnet 5 | $0.00013 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
worktrees 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 8d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktrees
Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.
Each worktree is an isolated copy of Discord Manager: its own git checkout, its own gitignored .env when it needs one, and its own SQLite store. Parallel lanes never share state, so gates, seeded demo stores, and MCP sessions run concurrently across worktrees. The main checkout may be a live installation — a running daemon, a real bot token, a store with real data — so its files, its store, and its processes are never touched from a worktree.
Lifecycle
Create from the main checkout:
git worktree add ../discord-manager-worktrees/<lane> -b <branch> origin/main
cd ../discord-manager-worktrees/<lane>
pnpm install
A fresh worktree has no node_modules and no .env. The four gates (pnpm run lint, pnpm run tsc, pnpm run test:unit, pnpm run test:e2e) need no .env — both test harnesses provision their own throwaway stores. Running the product from a worktree (pnpm run mcp, a seeded demo store for a real-client session) needs a worktree-local .env whose DATABASE_PATH points inside the worktree — never the main checkout's store, and never a store another lane owns. .mcp.json spawns pnpm run mcp from the project directory it lives in, so a real MCP client session opened from a worktree talks to that worktree's store, which is exactly what the Definition of Done's live proof wants.
Remove a worktree from the main checkout once its branch has merged:
git worktree remove ../discord-manager-worktrees/<lane>
Run removal from the main checkout, never from inside the worktree being removed — removal deletes the shell's working directory, so every later command in the same chain fails (git exits 128 on a vanished cwd). Never chain removal behind a prerequisite with ; — it runs even when the prerequisite failed; confirm the merge actually landed, then remove as its own command.
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.
- 8d ago First seen · 44 lines · 65 tokens per session scan A 7e919a929e8f
worktrees is a skill published in the GitHub repository seasonedcc/discord-manager (3 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,147 once invoked, about $0.0003 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-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.