arxivist: Skill for Claude Code

.claude/skills/assign-to-workforce/SKILL.md

assign-to-workforce is a skill for Claude Code from agentculture/arxivist. It costs 188 tokens per session (2,739 once invoked), scanned A, a copy of assign-to-workforce, MIT.

A workflow for giving separate development tasks to parallel coding agents, each working in its own isolated Git worktree. A worktree is a separate working copy of the same repository, and TDD means writing tests to guide and check the code.

In plain words
What is it for?
Implementing a pre-approved development plan in dependency waves, assigning one agent to each task, reviewing the split plan, merging completed worktrees, and preparing the final pull request.
Why use it?
It lets independent tasks proceed at the same time while reducing conflicts between changes. The main agent merges each result only after tests provide a check on the implementation.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents.

This is agentculture/arxivist's own configuration. It tells Claude Code how to work on arxivist itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything arxivist configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is git worktree add ../worktrees/agent-<task-id> -b agent/<task-id>.

Reuse

Borrowing it

Nothing to install: this file belongs to agentculture/arxivist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/agentculture/arxivist/main/.claude/skills/assign-to-workforce/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/agentculture/arxivist

Made for: Claude Code.

Wrote 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.

agentmods badge for assign-to-workforce

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentculture/arxivist/assign-to-workforce/github.svg)](https://agentmods.dev/skills/agentculture/arxivist/assign-to-workforce)
Your own site
<a href="https://agentmods.dev/skills/agentculture/arxivist/assign-to-workforce"><img src="https://agentmods.dev/badge/skills/agentculture/arxivist/assign-to-workforce/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.

agentmods 80×15 button for assign-to-workforce

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentculture/arxivist/assign-to-workforce"><img src="https://agentmods.dev/badge/skills/agentculture/arxivist/assign-to-workforce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 188 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,739 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00188 $0.02739
Opus 5 $0.00094 $0.01370
Sonnet 5 $0.00038 $0.00548
Haiku 4.5 $0.00019 $0.00274

Measured 9d ago against content hash b1be47f76664, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

assign-to-workforce 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 9d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/assign-to-workforce.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

100% identical to assign-to-workforce — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/assign-to-workforce/SKILL.md · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

assign-to-workforce — fan out a converged plan's waves to parallel agents

The skill is named assign-to-workforce; the product/CLI it reads is the devague plan waves command. (The prior leg — turning a spec into a plan — is the sibling /spec-to-plan skill.)

assign-to-workforce takes a converged devague plan and fans out its dependency waves to parallel agents (subagents, teammate agents, or generalist agents) — one agent per task per wave — each working in an isolated git worktree. The main agent merges each completed worktree gated by TDD. The human owns exactly three gates: the exported spec, the implementation split plan, and the final PR.

The devague CLI is never orchestrated by devague itselfdevague plan waves describes the dependency graph (#20); it does not spawn agents, manage worktrees, mark tasks done, or pick a backend. The fan-out is the operator's job — this skill and the main agent perform it.

How to run

The entry point is scripts/assign-to-workforce.sh. Invoke it from the repository whose plan you are implementing (plans persist under .devague/ in the current directory):

bash .claude/skills/assign-to-workforce/scripts/assign-to-workforce.sh split-plan [--plan <slug>]
bash .claude/skills/assign-to-workforce/scripts/assign-to-workforce.sh waves    [--plan <slug>] [--json]
bash .claude/skills/assign-to-workforce/scripts/assign-to-workforce.sh help

It resolves the CLI portably — an installed devague on PATH (the normal case), falling back to uv run devague when you are inside the devague checkout, else an install hint. The split-plan subcommand reads devague plan waves --json and renders the human-facing implementation split plan: task map, proposed per-task agent + model assignment, and the go/no-go question. The waves subcommand forwards to devague plan waves verbatim.

Usage

Subcommand What it does
split-plan [--plan S] Read devague plan waves and print the implementation split plan — task map with per-task agent + model proposal — ready for human go/no-go review.
waves [--plan S] [--json] Forward to devague plan waves [--json]. Read-only; lists wave batches. On a converged plan exits 0 listing the waves.
help Print usage.

Read the full file on GitHub · 243 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 243 lines · 188 tokens per session scan A b1be47f76664

Subscribe to this mod's changes

assign-to-workforce is a skill published in the GitHub repository agentculture/arxivist (2 stars, last pushed 1mo ago), licensed MIT. It adds 188 tokens to every session and 2,739 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to assign-to-workforce, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens