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.
curl -O https://raw.githubusercontent.com/tensorbee/rdocx/main/.claude/commands/integrate-feature.mdgit clone --depth 1 https://github.com/tensorbee/rdocxWrote 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/tensorbee/rdocx/integrate-feature)<a href="https://agentmods.dev/commands/tensorbee/rdocx/integrate-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/integrate-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.
<a href="https://agentmods.dev/commands/tensorbee/rdocx/integrate-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/integrate-feature.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.00028 | $0.01738 |
| Opus 5.5 | $0.00011 | $0.00695 |
| Sonnet 5.5 | $0.00006 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
integrate-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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integrate-feature F-XXX work/- [--batch]
Bring one worker's finished F-ID onto the sprint branch. Run this only from
the canonical sprint worktree, after the worker has run
/complete-feature F-XXX --prepare.
--batch is the mode /run-sprint uses. It creates the local F-ID commit and
defers the sprint ledgers, the done status, consolidated verification and the
push to the end of the sprint run.
Acceptance reconciliation
Before consuming a worker's handoff, compare its A-ID evidence with the approved consumer map and test matrix. Verify the integrated callers still supply the same context and defaults. Qualify interactions introduced by neighboring stories with focused checks rather than assuming individually green workers compose. Keep unmet native, installed and corpus criteria pending in the existing records. A contributed patch's test count never substitutes for its linked issue's whole acceptance inventory.
Compare the worker's acknowledged plan/instruction revisions with the current canonical contract before squash integration. If they differ, reconcile the material changes and affected evidence with the owner first. Do not let an older worker plan overwrite a newer approved plan merely because Git merges it without a conflict. Preserve current decisions and re-review semantic changes.
Preconditions
-
Clean tree on
sprint/sNN, matchingdocs/sprints/CURRENT_SPRINT.md. -
F-XXX is
in-progressinCURRENT_SPRINT.mdandBACKLOG.md, with anOwnermatching the agent suffix on the named branch. -
The branch name matches
work/<fid-lower>-<agent>and its merge base is an ancestor of the current sprint branch. A worker that rebased onto something else is not integrable without a decision. -
The handoff validates. Extract
.claude/handoffs/F-XXX-ready.mdfrom the worker branch to a temporary path and run:git show work/<fid-lower>-<agent>:.claude/handoffs/F-XXX-ready.md > <tmp> python3 scripts/sprint_workflow.py validate-handoff <tmp> --fid F-XXX
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.
- 6d ago Changed · +16 lines 857072f58c79
- 11d ago Changed · +13 lines 8956a085a3ce
- 14d ago Changed · +11 lines 35f81a22f0d0
- 26d ago First seen · 118 lines · 28 tokens per session scan A 1c3fac1e007c
integrate-feature is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,738 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.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.