Borrowing it
Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/claim.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote 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/commands/swarm-ai-research/swarm/claim)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/claim"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/claim/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.
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/claim"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/claim.svg" alt="Reviewed on agentmods" width="80" 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.01020 |
| Opus 5 | $0.00000 | $0.00510 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
claim 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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claim
Atomic work-start. Claim a task before doing any work on it — this refuses if another session already holds it, which is the one thing that physically prevents two sessions from building the same feature (the 2026-07-22 duplicate- 7ge5 incident).
Usage
/claim <bead-id> — claim a task and start work
/claim status — show what you and every other session currently hold
/claim release <bead-id> — release when done (or handing off)
/claim check <bead-id> — verify you still hold it (used by the pre-commit gate)
Why this exists
bd update --status=in_progress is advisory — it doesn't stop a second session
from picking up the same bead. /claim routes work-start through an atomic
claim in the shared cross-worktree coordination DB
($MAIN_REPO_ROOT/runs/runs.db): the first session to claim a task wins, and
every other session is refused with the holder's name. No two sessions can
hold the same task, so no two sessions can duplicate the work.
Behavior
When you invoke /claim <bead-id>:
- Run
python -m swarm.agentgit claim claim <bead-id>. - If it prints
REFUSED: … already claimed by <session>(exit 2): STOP. Another session is on this. Run/claim status, pick differentbd readywork, or coordinate. Do not start the work. - If it prints
REFUSED: … declared wards exceed the track's stamped bounds(exit 3): the bead carries aWARDS:stamp from dispatch and what you declared (.agentgit/wards.json,$AGENT_WARDS, or--wards) would widen it — more turns, more depth, a permission the track lacks. Narrow the declaration or take another bead. The claim was not taken. Dry-run withpython -m swarm.agentgit wards check <bead-id>. - If it prints
CLAIMED …(exit 0): a marker is written to.agentgit/current-claim.jsonand the bead is setin_progress. Proceed. The marker also holds the effective ward set you run under (track stamp composed with your declaration; the stamp alone if you declared nothing) — including the negative spec the Auditor and retro verify against. The pre-commit hook will verify you still hold it at commit time — a collision there means someone took your task mid-flight. - When the task is shipped (or you hand off), run
/claim release <bead-id>.
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.
- 2d ago Changed · +24 lines 0e5c6b9d05b9
- 9d ago First seen · 54 lines · 0 tokens per session scan A c0071699a5a2
claim is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,020 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 commands, from other repositories
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
user-story-sprint
Plan a sprint by selecting stories based on capacity, dependencies, and priority.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.