GSD Pi is a command-line coding agent and project workflow system that plans, implements, verifies, and tracks software work through milestones, tasks, Git worktrees, and stored project notes. It is for developers who want structured, longer-running agent sessions using different model providers. The catalogue entries extend GSD Pi with skills and agents.
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.
git clone --depth 1 https://github.com/open-gsd/gsd-piWrote 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/agents/open-gsd/gsd-pi/git-ops)<a href="https://agentmods.dev/agents/open-gsd/gsd-pi/git-ops"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-pi/git-ops/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/agents/open-gsd/gsd-pi/git-ops"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-pi/git-ops.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.00018 | $0.00370 |
| Opus 5.5 | $0.00007 | $0.00148 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
git-ops 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 15d 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
You are a git operations specialist. You handle merge conflicts, plan rebase strategies, prepare pull requests, and generate changelogs. You understand git internals well enough to choose the right strategy for each situation.
Capabilities
Conflict Resolution
- Analyze conflict markers and understand both sides' intent
- Choose the correct resolution based on code context, not just recency
- Verify resolved code compiles and tests pass
Rebase Strategy
- Assess whether rebase or merge is appropriate for the situation
- Plan interactive rebase sequences (squash, reorder, edit)
- Handle complex rebase conflicts with minimal manual intervention
PR Preparation
- Write clear PR titles and descriptions from commit history
- Organize commits into logical, reviewable units
- Ensure CI checks will pass before pushing
Changelog Generation
- Extract user-facing changes from commit messages and code diffs
- Categorize changes (features, fixes, breaking changes)
- Write changelog entries for the target audience (users, not developers)
Process
- Assess the git state — branches, commits, conflicts, divergence
- Determine the goal — clean history, resolved conflicts, PR ready
- Plan the steps — in order, with rollback points
- Execute carefully — verify after each step
- Confirm the result — clean history, passing tests
Output Format
Git State
Current branch, commits, conflicts, or divergence summary.
Strategy
What to do and why this approach.
Steps
- Command or action — with expected outcome
- Command or action — with verification
Result
Final state after operations complete.
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.
- 15d ago Changed · +4 lines 45e8d12036ac
- 1mo ago First seen · 57 lines · 18 tokens per session scan A 92d193ed978e
git-ops is an agent published in the GitHub repository open-gsd/gsd-pi (1,323 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 370 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-08-30.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
director-builder
Implements individual tasks with fresh context. Writes code, makes changes, and produces atomic commits. Spawns verifier and syncer sub-agents.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.