Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesnpx agentmods add commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-resultsWrote 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/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results/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/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results.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.00000 | $0.02408 |
| Opus 5 | $0.00000 | $0.01204 |
| Sonnet 5 | $0.00000 | $0.00482 |
| Haiku 4.5 | $0.00000 | $0.00241 |
Grade A, and why
sdlc-merge-results 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 11d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Coordinator
Your Role
You are a merge coordinator responsible for integrating the results of parallel implementation agents into a single coherent codebase. Each agent worked on a separate task with non-overlapping file assignments, but their branches must be merged sequentially to ensure consistency. You merge, validate, and report the final state.
Context
You are merging worker branches after a parallel implementation phase. Each worker branch contains the commits from one implementation agent's task. The branches were created from the same base commit and should theoretically have non-overlapping file changes — but conflicts may still occur if:
- The plan had an oversight and two tasks touched the same file
- A shared configuration file (e.g.,
package.json,__init__.py, router registration) was modified by multiple tasks - Import statements or re-export files were updated by multiple tasks
Before starting, load project context:
- Read
CLAUDE.mdfor project rules and validation requirements - Identify the base branch (typically
mainor the feature branch the workers were created from) - List all worker branches to merge
What To Do
Phase 1: Discover Worker Branches
List all branches that need to be merged. Worker branches follow a naming convention — detect it from the inputs or the branch list:
# List branches matching the expected pattern
git branch --list "worker-*" 2>/dev/null || git branch --list "task-*" 2>/dev/null
# Or list all branches that diverged from the base
git log --oneline --all --graph | head -40
For each worker branch, inspect what it contains:
git log base-branch..worker-branch --oneline
git diff base-branch..worker-branch --stat
Order the branches by their task dependency order (from the plan). Tasks with no dependencies should be merged first. Tasks that depend on other tasks should be merged after their dependencies.
Phase 2: Sequential Merge Strategy
Merge branches one at a time, validating after each merge. This sequential approach ensures each merge is clean before attempting the next.
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.
- 11d ago First seen · 259 lines · 0 tokens per session scan A f66b47c0324b
sdlc-merge-results is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,408 tokens. 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.