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/fideguch/my_pm_tools/git-workflownpx skills add fideguch/my_pm_tools --skill git-workflowgit clone --depth 1 https://github.com/fideguch/my_pm_toolsWhat 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.00000 | $0.01775 |
| Opus 5 | $0.00000 | $0.00888 |
| Sonnet 5 | $0.00000 | $0.00355 |
| Haiku 4.5 | $0.00000 | $0.00178 |
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 2d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git ワークフロー & ブランチ戦略スキル
メタデータ
- トリガー: 「Gitワークフロー設定」「ブランチ戦略」「Git運用ルール」「コミット規約」
- 前提条件: Git リポジトリが初期化済み
概要
チーム開発に最適な Git ワークフロー（GitHub Flow ベース）とコミット規約を設定するスキル。 Conventional Commits、ブランチ命名規則、PR テンプレートを一括整備する。
Phase 1: ブランチ戦略
1.1 GitHub Flow（推奨）
main（本番）
├── feature/add-login-page
├── fix/user-validation-error
├── refactor/api-layer
└── docs/update-readme
1.2 ブランチ命名規則
| プレフィックス | 用途 | 例 |
|---|---|---|
feature/ |
新機能 | feature/user-authentication |
fix/ |
バグ修正 | fix/login-redirect-loop |
refactor/ |
リファクタリング | refactor/api-error-handling |
docs/ |
ドキュメント | docs/api-reference |
infra/ |
インフラ | infra/ci-pipeline |
test/ |
テスト追加 | test/payment-integration |
hotfix/ |
緊急修正 | hotfix/security-vulnerability |
Phase 2: Conventional Commits
2.1 コミットメッセージ形式
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
2.2 Type 一覧
| Type | 説明 | SemVer |
|---|---|---|
feat |
新機能 | MINOR |
fix |
バグ修正 | PATCH |
docs |
ドキュメント | - |
style |
フォーマット変更（動作に影響なし） | - |
refactor |
リファクタリング | - |
perf |
パフォーマンス改善 | - |
test |
テスト追加・修正 | - |
build |
ビルド関連 | - |
ci |
CI/CD変更 | - |
chore |
その他の変更 | - |
2.3 例
feat(auth): ソーシャルログイン機能を追加
Google OAuth 2.0 による認証フローを実装。
セッション管理にJWTを使用。
Closes #123
2.4 commitlint 設定（オプション）
npm install --save-dev @commitlint/cli @commitlint/config-conventional
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.
- 2d ago First seen · 251 lines · 0 tokens per session scan A ddeed13fd54f
git-workflow is a skill published in the GitHub repository fideguch/my_pm_tools (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,775 tokens. 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
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
commit
Analyze changes, write a conventional commit, and (when shipping) open a PR with closing keywords so referenced issues auto-close on merge. Use when the user asks to commit, push, or open a PR.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
commit_push
Format code, review changes, commit, and push to remote.
contribution-guidelines
Contribution process with PR workflow, code review standards, commit conventions, and open source best practices.