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 troyjthomas/ios-agent-skills --skill git-workflowgit clone --depth 1 https://github.com/troyjthomas/ios-agent-skillsWrote 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/troyjthomas/ios-agent-skills/git-workflow)<a href="https://agentmods.dev/skills/troyjthomas/ios-agent-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/git-workflow/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/troyjthomas/ios-agent-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/git-workflow.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.00064 | $0.02441 |
| Opus 5.5 | $0.00026 | $0.00976 |
| Sonnet 5.5 | $0.00013 | $0.00488 |
| Haiku 4.5 | $0.00006 | $0.00244 |
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 1mo 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Parallel workstreams are powerful until they step on each other. This skill prevents that.
Branching Convention
Every Conductor workspace creates its own branch automatically. Name your workspaces descriptively:
workspace: build-projects-home → branch: build-projects-home
workspace: build-settings-flow → branch: build-settings-flow
workspace: build-explore-tab → branch: build-explore-tab
Branch-per-Iteration Rhythm
Whether you're in Conductor or running a single Claude Code session, the rhythm that works on production builds:
-
Always branch from a freshly-pulled
main. Never reuse old branches across iterations:git checkout main && git pull origin main && git checkout -b feat/<topic>Reusing branches accumulates stale state, makes diffs unreviewable, and re-introduces fixes you already merged.
-
Open a PR on the FIRST commit, not at the end. A PR is a conversation, not a deliverable. Pushing the first commit and opening a PR immediately:
- Surfaces the change to anyone watching the repo
- Lets CI run early (catches build / lint failures before you've layered more on top)
- Gives reviewers a stake in the iteration before it's locked in
-
Push eagerly. After every meaningful commit,
git push. The branch is more valuable on the remote than on your machine. If your laptop dies mid-iteration, the work isn't lost. -
One topic per branch. If you find yourself fixing two unrelated things, stop and split into two branches. Reviews stay tight; reverts stay surgical.
-
After every merge, the re-sync ritual. Local
mainneeds to be in sync with remotemainbefore you start the next branch — otherwise tools like Xcode that read from your working directory keep showing the old code:git fetch origin && git checkout main && git pull origin mainMake this a reflex. It prevents an entire class of "I fixed it but it's still broken on simulator" confusion.
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.
- 1mo ago First seen · 253 lines · 64 tokens per session scan A 92ecba302da7
git-workflow is a skill published in the GitHub repository troyjthomas/ios-agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 2,441 once invoked, about $0.0003 per session on Opus 5.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
codex-ops
Codex and Claude operating workflow for Memoire - JSON-first commands, commit hygiene, review loops, memory capture, and safe autonomous repo operation.
hermes-agent-bridge
Run Hermes Agent from Memoire with CLI, skills, toolsets, worktree, and session recipes.
asc-workflow
Define, validate, and run repo-local multi-step automations with asc workflow and .asc/workflow.json. Use when migrating from lane tools, wiring CI pipelines, or orchestrating repeatable asc + shell release flows with hooks, conditionals, and sub-workflows.
app-store-changelog
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR…
asc-build-lifecycle
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.