rdocx: Command for Claude Code

.claude/commands/claim-feature.md

claim-feature is a command for Claude Code from tensorbee/rdocx. It costs 24 tokens per session (946 once invoked), scanned A, original, MIT.

A workflow command that assigns a feature story to one worker and creates an isolated Git branch and worktree for it. Git is the version-control system used to track code and branches.

In plain words
What is it for?
Use it to claim a pending F-ID from the canonical sprint worktree for either Claude or Codex, after an approved design plan exists.
Why use it?
It prevents parallel workers from editing the same files or claiming the same story. Its checks stop work from starting when the sprint or design-plan state is not ready.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

This is tensorbee/rdocx's own configuration. It tells Claude Code how to work on rdocx 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 rdocx configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/sprint_workflow.py mark-feature SNN F-XXX approved \.

Reuse

Borrowing it

Nothing to install: this file belongs to tensorbee/rdocx. 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/tensorbee/rdocx/main/.claude/commands/claim-feature.md
Clone the repo
git clone --depth 1 https://github.com/tensorbee/rdocx

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 claim-feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/tensorbee/rdocx/claim-feature/github.svg)](https://agentmods.dev/commands/tensorbee/rdocx/claim-feature)
Your own site
<a href="https://agentmods.dev/commands/tensorbee/rdocx/claim-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/claim-feature/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 claim-feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/tensorbee/rdocx/claim-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/claim-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 946 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 original No closer match found 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.00024 $0.00946
Opus 5.5 $0.00010 $0.00378
Sonnet 5.5 $0.00005 $0.00189
Haiku 4.5 $0.00002 $0.00095

Measured 6d ago against content hash 162126da60e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

claim-feature 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 6d 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.

.claude/commands/claim-feature.md · 97 lines

How it starts

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

/claim-feature F-XXX

Assign one story to one worker so two sessions cannot write the same tree. Run this only from the canonical sprint worktree, never from a worker's.

/run-sprint performs claims itself and does not ask separately. Invoke this by hand when you are driving a parallel sprint manually.

Preconditions

Check all of these before touching anything. If one fails, name it and stop without altering sprint state, branches or worktrees.

  1. The branch is sprint/sNN matching the heading in docs/sprints/CURRENT_SPRINT.md.

  2. The tree is clean, with one exception. The approved design plan for F-XXX may be present and uncommitted, because a manual /design leaves it there. Refuse every other staged, unstaged or untracked path. Without this exception the claim would be impossible, since it needs both an approved plan and a clean tree.

  3. F-XXX is pending in both docs/sprints/CURRENT_SPRINT.md and docs/sprints/BACKLOG.md.

  4. .claude/plans/F-XXX-design.md exists and is approved, with non-empty ## Spec reference, ## Test plan, ## Risk routing and ## HLD impact sections. A whole-document spec citation is a failure here, the same as it is in /start-feature.

  5. The owner is the actual lowercase implementing host identity, such as claude, codex or grok, using only lowercase letters, digits and hyphens. Do not impersonate another model to fit an old example.

  6. The worktree path is given explicitly and does not exist. Do not infer a path and do not delete one. Put it outside the repository, as a sibling directory.

  7. work/<fid-lower>-<agent> does not exist, locally or on the remote.

The claim

  1. Set F-XXX to in-progress in CURRENT_SPRINT.md and BACKLOG.md.
  2. Write the agent name into the Owner cell of the current-sprint wave row. Unclaimed rows keep -.
  3. Regenerate the AUTOGEN counts in BACKLOG.md.
  4. Stage the claim plus the approved design plan, nothing else, and commit to the sprint branch:

Read the full file on GitHub · 97 lines

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. 6d ago Changed · +3 lines 162126da60e5
  2. 26d ago First seen · 94 lines · 24 tokens per session scan A 6510b14bc8b7

Subscribe to this mod's changes

claim-feature is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 946 once invoked, about $0.0001 per session on Opus 5.5. 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-10-04.