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 agents/ccdawn/vibelution/worktree-collaborationgit clone --depth 1 https://github.com/CCDawn/VibelutionWrote 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/agents/ccdawn/vibelution/worktree-collaboration)<a href="https://agentmods.dev/agents/ccdawn/vibelution/worktree-collaboration"><img src="https://agentmods.dev/badge/agents/ccdawn/vibelution/worktree-collaboration.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02675 |
| Opus 5 | $0.00000 | $0.01337 |
| Sonnet 5 | $0.00000 | $0.00535 |
| Haiku 4.5 | $0.00000 | $0.00267 |
Grade A, and why
worktree-collaboration 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 3d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Worktree Collaboration
This document defines the default collaboration protocol for multiple Agents working on Vibelution in parallel.
Work Surfaces
<project-root>is the durable localmainintegration workspace. Keep this path checked out on branchmain; use it only for local syncing, fast-forward merging, merge-result inspection, and publishing after the user explicitly authorizes a GitHub sync/release. All validation must finish before merge. Direct development writes and commits onmainare forbidden.- If
<project-root>is found on a non-main branch, preserve or migrate that work into<project-root>\.worktrees\<task-slug>or a named stash, then restore the root path tomainbefore continuing normal development or integration. - Development Agents use task-specific worktrees under
<project-root>\.worktrees\. Resolve the pool withcore.infrastructure.branch_workspace; do not hardcode a username, Desktop, or sibling folder. - The old sibling folder
<project-root-parent>\Vibelution-worktrees\no longer exists on disk. The compatibility layer (migrate_legacy_branch_workspacesincore.infrastructure.branch_workspace) is kept only in case the folder reappears. Do not create new checkouts there; live legacy trees, if any ever resurface, can move withmigrate_legacy_branch_workspaces. - If the in-repo pool is unavailable, use
.claude/worktrees\<task-slug>or another explicit task worktree path and record the actual path incheck/claimevidence. - Each active task, including
FAST_PATCH, gets one task worktree and onecodex/<task-slug>branch.FAST_PATCHmay use a lighter validation path, but it may not stay in themainworkspace. Do not reuse an old task worktree for a new goal.
Starting A Task
For STANDARD_TASK and HIGH_RISK, create a task branch from the current local main:
cd <project-root>
git worktree add .worktrees/<task-slug> -b codex/<task-slug> main
Use git fetch origin only as a read-only observation step unless the user explicitly asks to align with GitHub. Do not reset, rebase, or create task branches from origin/main by default.
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.
- 3d ago First seen · 191 lines · 0 tokens per session scan A 39ef4e551bfc
worktree-collaboration is an agent published in the GitHub repository CCDawn/Vibelution (21 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,675 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 agents, from other repositories
medical-learning-safety-reviewer
审校医学学习草稿的来源、教育边界、患者隐私和输出风险；只返回审校意见，不处理外部动作或状态写入。.
guideline-learning-designer
将主助手已核验的指南材料组织成安全、可继续展开的学习地图、流程关系、学习诊断或复习路径；不处理真实患者决策。.
ingest-doc
Ingest one document (local file or web URL) into an AKB vault as a five-section LLM-wiki summary page, optionally preserving the original bytes in the raw file layer.
ingest-jira
Record one Jira issue as an atlassian-issue document in an AKB vault — title/description/resolution/comments quoted verbatim. Fetched live via the Atlassian MCP server; always upsert.
ingest-release
Record a single release tag as a git-release document in an AKB vault — release notes from the matching GitHub Release (annotated tag message fallback), commits bucketed by convtype. Requires range commits pre-ingested.
idea-drafter
Generate creative ideas inspired by the session — architecture improvements, product concepts, workflow innovations, and technical possibilities.