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 instructions/rohansx/workz/claude-mdgit clone --depth 1 https://github.com/rohansx/workzWrote 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/instructions/rohansx/workz/claude-md)<a href="https://agentmods.dev/instructions/rohansx/workz/claude-md"><img src="https://agentmods.dev/badge/instructions/rohansx/workz/claude-md.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.00297 | $0.00297 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade B, and why
workz CLAUDE.md scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Or add manually to your Claude Code config (`~/.claude/settings.json`): What it actually says
workz MCP Integration
workz exposes all its operations as MCP tools so AI agents can manage worktrees directly.
Setup
claude mcp add workz -- workz mcp
Or add manually to your Claude Code config (~/.claude/settings.json):
{
"mcpServers": {
"workz": {
"command": "workz",
"args": ["mcp"]
}
}
}
Available Tools
| Tool | Description |
|---|---|
workz_start |
Create a worktree with auto-synced deps and env |
workz_list |
List all worktrees as JSON |
workz_status |
Rich status: branch, dirty state, last commit |
workz_sync |
Sync symlinks/env into an existing worktree |
workz_done |
Remove a worktree (with optional force) |
workz_conflicts |
Detect files modified in multiple worktrees |
Parallel Agent Workflow
To run parallel agents on independent tasks:
- Use
workz_startto create isolated worktrees for each task - Each agent gets its own branch, deps, env — no interference
- Use
workz_conflictsto check for overlapping file changes before merging - Use
workz_doneto clean up when finished
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.
- 4d ago First seen · 43 lines · 297 tokens per session scan B 904a91547a03
workz CLAUDE.md is an instructions file published in the GitHub repository rohansx/workz (83 stars, last pushed 1mo ago), licensed MIT. It adds 297 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
dev3000 AGENTS.md
Instructions for vercel-labs/dev3000, covering agents.md, runtime, local ui, production workflows, browser tools and development rules.
git-worktree-runner ai.instructions.md
Instructions for coderabbitai/git-worktree-runner, covering ai adapter instructions, when to use a file vs registry, adding a standard ai tool (registry), adding a custom ai tool (file override) and toolname adapter.
vue-tui AGENTS.md
AGENTS.md instructions for vuejs-ai/vue-tui, covering common pitfalls & best practices, project context records (pcr), using vite+, the unified toolchain for the web and review checklist.
mulmoterminal CLAUDE.md
Claude Code instructions for receptron/mulmoterminal, covering claude.md — mulmoterminal, stack & package manager, run after changes, import a component at module scope, never inside a test and no emojis.
UniCli CLAUDE.md
Claude Code instructions for yucchiy/UniCli, covering unicli, project structure, quick commands, build protocol (must be built first to trigger file copy) and build client.
autospec AGENTS.md
Instructions for ariel-frischer/autospec, covering agents.md, prerequisites, commands, build & dev and single test.