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/danwahlin/ai-agent-board/git-workflownpx skills add DanWahlin/ai-agent-board --skill git-workflowgit clone --depth 1 https://github.com/DanWahlin/ai-agent-boardWrote 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/danwahlin/ai-agent-board/git-workflow)<a href="https://agentmods.dev/skills/danwahlin/ai-agent-board/git-workflow"><img src="https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/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.01557 |
| Opus 5 | $0.00008 | $0.00779 |
| Sonnet 5 | $0.00003 | $0.00311 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade C, and why
git-workflow scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If a worktree was deleted manually (rm -rf), `git worktree prune` recovers the state. This is a copy
100% identical to git-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Squad uses a three-branch model. All feature work starts from dev, not main.
| Branch | Purpose | Publishes |
|---|---|---|
main |
Released, tagged, in-npm code only | npm publish on tag |
dev |
Integration branch — all feature work lands here | npm publish --tag preview on merge |
insiders |
Early-access channel — synced from dev | npm publish --tag insiders on sync |
Branch Naming Convention
Issue branches MUST use: squad/{issue-number}-{kebab-case-slug}
Examples:
squad/195-fix-version-stamp-bugsquad/42-add-profile-api
Workflow for Issue Work
-
Branch from dev:
git checkout dev git pull origin dev git checkout -b squad/{issue-number}-{slug} -
Mark issue in-progress:
gh issue edit {number} --add-label "status:in-progress" -
Create draft PR targeting dev:
gh pr create --base dev --title "{description}" --body "Closes #{issue-number}" --draft -
Do the work. Make changes, write tests, commit with issue reference.
-
Push and mark ready:
git push -u origin squad/{issue-number}-{slug} gh pr ready -
After merge to dev:
git checkout dev git pull origin dev git branch -d squad/{issue-number}-{slug} git push origin --delete squad/{issue-number}-{slug}
Parallel Multi-Issue Work (Worktrees)
When the coordinator routes multiple issues simultaneously (e.g., "fix bugs X, Y, and Z"), use git worktree to give each agent an isolated working directory. No filesystem collisions, no branch-switching overhead.
When to Use Worktrees vs Sequential
| Scenario | Strategy |
|---|---|
| Single issue | Standard workflow above — no worktree needed |
| 2+ simultaneous issues in same repo | Worktrees — one per issue |
| Work spanning multiple repos | Separate clones as siblings (see Multi-Repo below) |
Setup
From the main clone (must be on dev or any branch):
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.
- 5d ago First seen · 205 lines · 16 tokens per session scan C 0591afc3b9be
git-workflow is a skill published in the GitHub repository DanWahlin/ai-agent-board (57 stars, last pushed 10d ago), licensed MIT. It adds 16 tokens to every session and 1,557 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to git-workflow, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
collattice
Operate a Collattice kanban board through its Model Context Protocol (MCP) endpoint — connecting, authentication, the board model, identifier rules (board-level reads need a board GUID, not a slug), the Markdown a board renders, and the full tool reference: reading and creating cards, moving and reordering lanes…
taskview
Conventions for browsing and managing TaskView projects, lists, and tasks through the bundled taskview MCP tools.
opencode-plugin-idioms
Event hook payload shapes, session lifecycle timing, toast/TUI-route render boundaries, and child-session tagging conventions for OpenCode server (@opencode-ai/plugin) and TUI (@opencode-ai/plugin/tui) plugins, grounded in the vendored OpenCode source at references/opencode.
self-align
Adversarial self-audit of the Kagan repo through four lenses — code quality & YAGNI, security, spec alignment, docs/AGENTS.md freshness — each finding self-assessed and reported by severity and confidence for the developer to action. Use only when explicitly asked to self-align, audit, or health-check the codebase; it…
appium-python-expert
Specialist skill for mobile E2E testing with Appium 2.x + Python (pytest) for Android and iOS. Use this skill whenever the user asks about: setting up Appium with Python, writing mobile test cases, configuring Android/iOS drivers (UIAutomator2, XCUITest), implementing Page Object Model for mobile, running tests with…
selenium-cucumber-expert
Use when writing E2E tests with Selenium WebDriver and Cucumber BDD in Java, setting up BDD test infrastructure with Maven or Gradle, writing Gherkin feature files, implementing step definitions in Java, configuring Page Object Model or Screenplay Pattern, setting up parallel execution, generating ExtentReports or…