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/moabualruz/fulcrum/worktree-policygit clone --depth 1 https://github.com/moabualruz/fulcrumWrote 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/moabualruz/fulcrum/worktree-policy)<a href="https://agentmods.dev/agents/moabualruz/fulcrum/worktree-policy"><img src="https://agentmods.dev/badge/agents/moabualruz/fulcrum/worktree-policy.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.1 | $0.00000 | $0.00383 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
worktree-policy 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 5d 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.
What it actually says
Worktree Policy
Every PRD-driven adoption slice runs in its own git worktree. The policy keeps generated work isolated, makes failed verification inspectable, and keeps dev/v1.0 as the only merge target.
Lifecycle
- Select one eligible PRD from the local PRD glossary (kept locally, not tracked).
- Create
.claude/worktrees/<id>/fromdev/v1.0on branchfeat/prd-<id>. - Implement only the PRD's assigned paths unless verification exposes a directly related prerequisite.
- Run every command in the PRD's
verifylist. - Run
bun run typecheckandbun run lint. - Commit the slice in the PRD worktree when all gates exit 0.
- Fast-forward merge
feat/prd-<id>intodev/v1.0. - Prune
.claude/worktrees/<id>/.
Verify-Fail Recovery
If any verify command fails, stop the slice before merge.
- Leave
.claude/worktrees/<id>/intact for inspection. - Update the PRD entry with
status: "blocked",blocked_reason, andblocked_at. - Append a
BLOCKED:<id>line to the adoption progress log. - Do not flip
passestotrue. - Do not prune the worktree until a later pass resolves the blocker.
Merge Rules
- Use fast-forward merges only.
- Never merge a dirty worktree.
- Never force-push or reset shared branches to recover a PRD slice.
- If
dev/v1.0moved, rebase the PRD branch inside its worktree, rerun all gates, then merge. - Keep one commit per PRD unless a separate prerequisite fix is required and verified independently.
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.
- 5d ago First seen · 33 lines · 0 tokens per session scan A 0f3f387a94b3
worktree-policy is an agent published in the GitHub repository moabualruz/fulcrum (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 383 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-31.
Other agents, from other repositories
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…
rondoflow-i18n-translator
Translates RondoFlow UI strings into Slovak (sk) and Spanish (es) and writes them into the locale catalogs, keeping key/interpolation parity with English so the catalog test passes. Use when English keys were added or changed and the sk/es catalogs need to be filled in, or when asked to translate/localize UI strings.…
board-opus
Design-taste and architecture executor on the delivery board (opus tier). Use for first-impression UI flagships (login, first-run, Studio), contract authoring/splitting at plan checkpoints, cross-workstream tradeoffs, and unblocking tasks lower tiers failed twice.
board-sonnet
Standard delivery-board contract executor (sonnet tier). Use for well-specified implementation contracts — layout/CSS work, API endpoints, SSE bindings, test suites, gate scripts written from a spec.
board-verifier
Independent verifier for delivery-board tasks (haiku tier, fresh context). Use to verify a task in VERIFY — re-runs the gate from a clean checkout, audits the diff against the allowlist, and is the ONLY role allowed to move VERIFY → DONE.
board-haiku
Mechanical delivery-board executor (haiku tier). Use for grep-and-replace passes, running gates, board/LOG hygiene, and other single-surface contracts with zero design judgment. Also see board-verifier for verification work.