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/barkain/claude-code-workflow-orchestration/claude-mdgit clone --depth 1 https://github.com/barkain/claude-code-workflow-orchestrationWrote 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/barkain/claude-code-workflow-orchestration/claude-md)<a href="https://agentmods.dev/instructions/barkain/claude-code-workflow-orchestration/claude-md"><img src="https://agentmods.dev/badge/instructions/barkain/claude-code-workflow-orchestration/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.04519 | $0.04519 |
| Opus 5 | $0.02259 | $0.02259 |
| Sonnet 5 | $0.00904 | $0.00904 |
| Haiku 4.5 | $0.00452 | $0.00452 |
Grade B, and why
claude-code-workflow-orchestration 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.
cat .claude/state/delegation_violations.json # current per-turn nudge counter How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Delegation Policy (Soft Enforcement)
The framework nudges via stderr when the main agent uses work-doing tools (Bash, Edit, Write, Glob, Grep, MultiEdit, NotebookEdit) directly. Nudges never block. They escalate by per-turn violation count: silent → imperative STOP → imperative STOP (2nd call phrasing) → strong reminder explaining what's being lost. The counter resets each turn and zeros when /workflow-orchestrator:delegate runs. Read is not tracked — direct user-requested file reads are allowed.
The expected path for any multi-step or work-shaped request is:
/workflow-orchestrator:delegate <task description>
Subagents are immune (they're executing a delegation). New tools added by Claude Code never trigger nudges — only the 7 stable work primitives are tracked.
Prerequisites
- uv - Python package manager (required for
uvx,uv run) - bun - JavaScript runtime (for ccusage cost tracking in statusline)
- jq - JSON processor (optional, for advanced features)
No pyproject.toml exists — all scripts use uv run --no-project --script mode.
Build, Lint, and Test Commands
uvx ruff format . # Format code (auto-fix)
uvx ruff check --no-fix . # Lint code (check only)
uvx pyright . # Type checking
uvx deadcode hooks/ scripts/ # Dead code detection
The PostToolUse hook enforces a specific ruff rule subset on edited Python files:
uvx ruff check --select F,E711,E712,UP006,UP007,UP035,UP037,T201,S <file>
CI workflow exists (.github/workflows/ci.yml) but tests are currently disabled/placeholder.
Available Commands
/workflow-orchestrator:delegate <task> # Plan and execute task via native plan mode
/workflow-orchestrator:add-statusline # Enable workflow status display
Installation:
- Plugin:
claude plugin install workflow-orchestrator@barkain-plugins - Manual:
./install.sh [--scope=user|project]
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 · 299 lines · 4,519 tokens per session scan B 4c260f58e51e
claude-code-workflow-orchestration CLAUDE.md is an instructions file published in the GitHub repository barkain/claude-code-workflow-orchestration (84 stars, last pushed 1mo ago), licensed MIT. It adds 4,519 tokens to every session, about $0.0226 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
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
my-claude-skills CLAUDE.md
Instructions for brody-0125/my-claude-skills, covering claude code skills repository, validation commands, sub-kopring-engineer: kotlin/java 코드 컨벤션 검증, numerical: 수치 연산 코드 검증 and sub-test-engineer: 문서 일관성 검증.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).