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 skills add web3dev1337/agent-workspace --skill orchestrator-worktree-conventionsgit clone --depth 1 https://github.com/web3dev1337/agent-workspaceWrote 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/web3dev1337/agent-workspace/orchestrator-worktree-conventions)<a href="https://agentmods.dev/skills/web3dev1337/agent-workspace/orchestrator-worktree-conventions"><img src="https://agentmods.dev/badge/skills/web3dev1337/agent-workspace/orchestrator-worktree-conventions/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/web3dev1337/agent-workspace/orchestrator-worktree-conventions"><img src="https://agentmods.dev/badge/skills/web3dev1337/agent-workspace/orchestrator-worktree-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.00664 |
| Opus 5.5 | $0.00028 | $0.00266 |
| Sonnet 5.5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
orchestrator-worktree-conventions 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Worktree Conventions
Overview
This skill defines the standard directory layout and worktree naming conventions used by Agent Orchestrator so agents can reliably create, find, and manage projects/worktrees.
Quick Rules
- Never edit the user’s run-only orchestrator instance: avoid
~/GitHub/tools/automation/claude-orchestrator/master(it’s used on port 3000). Do all orchestrator dev work in.../claude-orchestrator-dev. - Prefer the worktree layout: each project has a stable
master/folder plus multipleworkN/folders (e.g.,work1…work8) for parallel work. - Keep paths deterministic: the orchestrator and scripts should be able to derive category/framework/project/worktree from folder location.
Standard Directory Layout
Base root: ~/GitHub/
Typical project path:
~/GitHub/<category>/<framework>/<project>/<worktree>
Where <worktree> is usually:
master(stable “mainline” checkout)work1,work2, … (parallel dev worktrees)
Examples:
~/GitHub/games/hytopia/HyFire2/master~/GitHub/games/hytopia/HyFire2/work1~/GitHub/websites/<project>/master
Some categories may have “ungrouped” projects directly under the category folder; treat them as valid and don’t force nesting.
For more examples, see references/layout.md.
Creating a New Project (Recommended Path)
Prefer using the orchestrator’s Greenfield Wizard (UI) so the repo is created consistently and worktrees are initialized correctly.
When asked to “create a new project”, gather:
- Desired category + framework (games/hytopia, games/monogame, websites, tools, writing, etc.)
- Project name
- Whether it should be worktree-structured immediately (default: yes)
- Any known default port (avoid 3000; prefer 4000+ for local dev services)
Adding a New Worktree
Preferred workflow:
- Use the orchestrator UI to add a worktree to the active workspace.
- Name it with the next available number (e.g., if you have
work1..work3, creatework4).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 64 lines · 70 tokens per session scan A e400396d1296
orchestrator-worktree-conventions is a skill published in the GitHub repository web3dev1337/agent-workspace (35 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 664 once invoked, about $0.0003 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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.