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/apexiq/skillsmith/git_workflownpx skills add ApexIQ/skillsmith --skill git_workflowgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/git_workflow)<a href="https://agentmods.dev/skills/apexiq/skillsmith/git_workflow"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/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.00024 | $0.00495 |
| Opus 5 | $0.00012 | $0.00247 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
What it actually says
🌳 Git Workflow
Rule: Good git hygiene makes debugging and collaboration 10x easier.
1. Branching Strategy
| Branch | Purpose | Merges To |
|---|---|---|
main |
Production-ready code | - |
develop |
Integration branch | main |
feature/<name> |
New features | develop |
fix/<name> |
Bug fixes | develop or main (hotfix) |
- Naming:
feature/add-command-palette,fix/email-sync-timeout.
2. Commit Messages (Conventional Commits)
<type>(<scope>): <short description>
<body - optional>
| Type | Use Case |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code change that doesn't fix a bug or add a feature |
docs |
Documentation only |
test |
Adding or fixing tests |
chore |
Build process, dependencies |
Examples:
feat(inbox): add command palette (Cmd+K)fix(sync): handle timeout errors gracefullyrefactor(rules): extract validation logic to service
3. Pull Request Conventions
- Title: Same format as commit message.
- Description:
- What: 1-2 sentences on the change.
- Why: Link to issue/task.
- How to test: Steps for reviewer.
- Size: <300 lines. Larger PRs should be split.
Examples
- Good PR:
feat(dashboard): add priority radar component- 150 lines, tests included. - Bad PR:
updates- 800 lines, no description, touches 20 files.
Guidelines
- Commit often, push daily.
- Rebase feature branches on
developbefore PR. - Squash commits when merging to keep history clean.
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 · 64 lines · 24 tokens per session scan A ac8e5d8f1a18
git-workflow is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 495 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
oad/commit
EvoFlux workflow for well-formatted, detailed conventional commits.
commit
Create a git commit for the Vision-Agents repo.
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…