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 rockyflux/yq-workflow --skill yq-git-helpergit clone --depth 1 https://github.com/rockyflux/yq-workflowWrote 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/rockyflux/yq-workflow/yq-git-helper)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/yq-git-helper"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-git-helper/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/rockyflux/yq-workflow/yq-git-helper"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/yq-git-helper.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.00030 | $0.00657 |
| Opus 5 | $0.00015 | $0.00329 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
yq-git-helper 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 8d 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
YQ Git Helper
Overview
整理分支、提交、PR 描述和合并前检查，让技术改动能被清晰、规范地交付出去。
Core principle: 交付不只是把代码推上去，还要让他人能理解、评审和接手。
When to Use
- 用户要整理提交、写 PR、准备合并或发布说明
- 需要把一组改动收成清晰的交付单元
- 需要补充变更摘要、验证结果和风险说明
- 需要确认当前分支是否具备合并条件
Route Elsewhere
- 主要是实现功能：转
yq-code-gen - 主要是代码质量审查：转
yq-code-review - 主要是运行或技术文档：转
yq-doc-gen
Process
- 整理改动范围、目的和验证结果。
- 归纳 commit 主题和 PR 主叙事。
- 检查测试、文档、风险说明和回滚准备。
- 标出 reviewer 最需要先看的点。
- 输出合并前的剩余阻塞项或建议动作。
Output
# Git Delivery Summary
## Branch Purpose
## Change Summary
## Validation
## Risks and Notes
## PR Description Draft
## Merge Readiness
## Recommended Next Step
Related Skills
- 上游通常来自
yq-code-review、yq-doc-gen - 完成前验证可参考
superpowers:verification-before-completion - 分支收口流程可参考
superpowers:finishing-a-development-branch
Recommended Next Step
- 默认先走
superpowers:verification-before-completion，确认交付说法和验证证据一致 - 需要继续收口分支、提交和合并动作时，接
superpowers:finishing-a-development-branch
Common Mistakes
- 提交信息不能反映真实改动意图
- PR 只有“做了什么”，没有“为什么”和“怎么验证”
- 合并前没有显式列出风险和阻塞项
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.
- 8d ago First seen · 85 lines · 30 tokens per session scan A 59078eca415e
yq-git-helper is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 657 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.