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 vmobifystudio/app-dev-team --skill git-pr-strategygit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/git-pr-strategy)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/git-pr-strategy"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/git-pr-strategy/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/vmobifystudio/app-dev-team/git-pr-strategy"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/git-pr-strategy.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.00026 | $0.00350 |
| Opus 5.5 | $0.00010 | $0.00140 |
| Sonnet 5.5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
git-pr-strategy 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.
What it actually says
Git and PR strategy
Use for every code or documentation change that will be reviewed, merged, released, reverted, or
shared with another agent. Read knowledge/git-workflow.md and agent-isolation first.
Lifecycle
- Run context preflight and confirm the base branch, ticket, worktree, and dirty-tree state.
- Use one worktree per writing agent and one ticket per branch. Never stage blindly.
- Keep commits coherent and reversible: implementation, tests, docs, and generated artifacts should be distinguishable when that helps review. Do not rewrite another agent's branch.
- Before review, update from the declared integration branch and rerun the relevant gates. A review is stale when the source commit or required evidence changes.
- The reviewer owns the verdict; the author fixes findings. No self-approval, no merge on a summary, and no merge while required checks are unknown.
- Resolve conflicts by reading both sides and the governing spec. Never choose “ours” or “theirs” blindly. If the conflict changes behavior or contract, escalate to the owner of that contract.
- Record the merge commit/tag, checks, evidence bundle, and rollback/revert path in the release record.
Communication
Use the team ledger for material decisions, blockers, escalations, and handoffs. State what changed, what was verified, what remains unknown, and the exact next action. Do not hide a failed command behind “could not run”; name the missing toolchain or input.
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 · 30 lines · 26 tokens per session scan A 9951cc7baf0f
git-pr-strategy is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 350 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
git-workflow
Branch naming, commit message format, and PR conventions. Use when making git commits or creating PRs.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.