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 skills add xiqin/loom --skill loom-finishing-a-development-branchgit clone --depth 1 https://github.com/xiqin/loomWrote 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/skills/xiqin/loom/loom-finishing-a-development-branch)<a href="https://agentmods.dev/skills/xiqin/loom/loom-finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-finishing-a-development-branch/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/skills/xiqin/loom/loom-finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/xiqin/loom/loom-finishing-a-development-branch.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.00052 | $0.00937 |
| Opus 5 | $0.00026 | $0.00468 |
| Sonnet 5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
loom-finishing-a-development-branch 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 11d 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.
What it actually says
开发分支收尾
触发条件
loom-verification-before-completion验证通过loom-index-update索引已更新- 用户确认所有开发工作已完成
完成条件与下一步
- 分支已合并到主分支 / PR 已创建 / 分支已保留
- 功能开发流程结束
公告
开始时宣布："我正在使用 loom-finishing-a-development-branch skill 来完成这项工作。"
执行流程
Step 1：确认开发完成
- 所有 task 已完成
- 所有测试通过
- 图后端状态已确认（不可用时已注明跳过）
- 无 BLOCKER
- 测试报告已生成（来自 test-reporter）
Step 2：检查分支状态
git status
git diff --stat
- 确认所有变更已暂存
- 确认没有意外的文件变更
- 确认不在主/主分支上
Step 3：运行最终验证
构建/检查/测试命令
读取 .loom/rules/constitution.md 中的 BUILD_CMD/VET_CMD/TEST_CMD 并执行验证。
Step 4：展示选项
向用户展示以下选项：
## 分支完成选项
**1. Merge（合并）** - 直接合并到主分支
**2. Pull Request** - 创建 PR 供审查
**3. Keep（保留）** - 保持分支，稍后继续
**4. Discard（丢弃）** - 丢弃所有变更
请选择？
Step 5：提交变更（如有未提交的变更）
如果分支上还有未提交的变更，先提交：
git add <specific-files>
git commit -m "$(cat <<'EOF'
feat: <功能描述>
- 变更 1
- 变更 2
Co-Authored-By: AI Assistant
EOF
)"
Step 6：执行用户选择
- Merge:
git checkout <branch> && git merge --no-ff feature/<date>-<name> && git push origin <branch> - Pull Request:
git push -u origin feature/<date>-<name>→gh pr create --title "feat: <描述>" --body "..." - Keep: 保持分支状态，提醒用户稍后继续
- Discard:
git checkout <branch> && git branch -D feature/<date>-<name>
提交信息规范
Conventional Commits 格式
提交信息必须遵循 Conventional Commits 格式：<type>(<scope>): <subject>
- feat: 新功能
- fix: Bug 修复
- refactor: 重构（不改变行为）
- docs: 文档
- test: 测试
- chore: 构建/工具变更
约束
- 提交前必须运行完整验证
- 提交信息必须清晰描述变更内容
- 禁止提交敏感信息（密钥、密码等）
禁止在主分支实现
没有明确用户同意，永远不要在 main/master 分支上开始实现。
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.
- 11d ago First seen · 122 lines · 52 tokens per session scan A 6df604bd9dcf
loom-finishing-a-development-branch is a skill published in the GitHub repository xiqin/loom (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 937 once invoked, about $0.0003 per session on Opus 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-08-31.
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.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
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.
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
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…