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 agentmods add skills/furkangonel/cowrangler/git-workflownpx skills add furkangonel/cowrangler --skill git-workflowgit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/git-workflow)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/git-workflow"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/git-workflow.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00742 |
| Opus 5 | $0.00008 | $0.00371 |
| Sonnet 5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
git-workflow 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 3d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow SOP
Branch Naming Convention
feature/<ticket>-short-description # New features
fix/<ticket>-short-description # Bug fixes
chore/<ticket>-short-description # Maintenance, deps, tooling
docs/<ticket>-short-description # Documentation only
refactor/<ticket>-short-description # Code restructuring
hotfix/<ticket>-short-description # Urgent production fixes
Conventional Commits Format
<type>(<scope>): <short description>
[optional body — explain WHY, not what]
[optional footer — BREAKING CHANGE: ..., Closes #123]
Types
| Type | When to use |
|---|---|
feat |
New user-visible feature |
fix |
Bug fix |
chore |
Build system, tooling, dependencies |
docs |
Documentation changes only |
refactor |
Code change that doesn't fix a bug or add a feature |
test |
Adding or fixing tests |
perf |
Performance improvement |
ci |
CI/CD pipeline changes |
revert |
Reverts a previous commit |
Good commit message examples
feat(auth): add OAuth2 Google login support
fix(api): handle null response from payment gateway
Closes #892. The gateway returns null instead of an error object
when the card is declined — we now normalize this to a proper error.
chore: upgrade typescript to 5.4 and fix type errors
BREAKING CHANGE: strict null checks now enforced everywhere
Standard Workflow
# 1. Start from fresh main
git checkout main && git pull
# 2. Create feature branch
git checkout -b feature/123-add-user-avatar
# 3. Make focused commits as you work
git add -p # Stage only what belongs to this commit
git commit -m "feat(users): add avatar upload endpoint"
# 4. Keep branch current with main
git fetch origin && git rebase origin/main
# 5. Before PR: squash if needed
git rebase -i origin/main
# 6. Push and open PR
git push -u origin HEAD
PR Description Template
## What
Brief description of what this PR does.
## Why
Why is this change needed? Link to issue/ticket.
## How
Key implementation decisions made and why.
## Testing
How was this tested? What should reviewers verify?
## Screenshots (if UI change)
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No console.log / debug code left
- [ ] Breaking changes documented
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.
- 3d ago First seen · 118 lines · 16 tokens per session scan A 25374ecbde22
git-workflow is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 742 once invoked, about $0.0001 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
ftshare-market-data
FTShare 市场数据技能集。根据用户对股票、ETF、指数、基金、可转债、期货、港股、美股、资金流、财务数据或宏观数据的查询意图，匹配并执行对应子 skill。.
eastmoney-stock-valuation
查询东财个股日估值。当用户需要查询全部 A 股个股的每日估值数据，包括市盈率（TTM/LYR）、市净率、市现率、市销率、PEG、总市值、流通市值、收盘价等；支持单票单日、单票历史区间及全市场查询，或了解东财个股日估值时使用。.
eastmoney-us-stock-daily-ohlc
查询东财美股历史日 K 线。当用户需要查询东财美股历史日 K 线；有日期范围时按 3 天窗口分批请求，无日期范围时全量拉取，或了解东财美股历史 OHLC、东财美股历史日 K 线时使用。.
etf-ohlcs
单只 ETF OHLC K 线（market.ft.tech）。用户问某只 ETF 的 K 线、日线/周线/月线、开高低收、前/后复权时使用。.
etf-prices
单只 ETF 分钟级分时价格（market.ft.tech）。用户问某只 ETF 分时、当日走势、多日分时、一分钟行情时使用。.
convertible-bond-candlesticks-batch
批量获取多只可转债 K 线 POST 接口（market.ft.tech，convertible-bond-candlesticks/batch）。用户问多只可转债的 K 线、批量可转债日 K/周 K/月 K/年 K 时使用。必填 --symbols、--interval-unit、--until-ts-millis；可选 --interval-value、--adjust-kind、--since-ts-millis、--limit。.