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 commands/ai-sdlc-framework/ai-sdlc/resolve-conflictsgit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/ai-sdlc-framework/ai-sdlc/resolve-conflicts)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/resolve-conflicts"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/resolve-conflicts.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.00085 | $0.02158 |
| Opus 5 | $0.00043 | $0.01079 |
| Sonnet 5 | $0.00017 | $0.00432 |
| Haiku 4.5 | $0.00009 | $0.00216 |
Grade A, and why
resolve-conflicts scanned grade A 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execFile } = await import('node:child_process'); How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manually invoke the ci-conflict-resolver subagent for PR
#$ARGUMENTS. This is the AISDLC-460 manual escape hatch — the watcher
will pick it up on the next tick anyway, but the operator sometimes
wants to drive the rebase + re-arm immediately (e.g. an auto-merge-armed
PR is stuck and you want it cleared before walking away).
Why this lives in a slash command (not the agent directly)
Plugin subagents cannot use the Agent tool (the harness filters it
out one level deep — empirical proof in AISDLC-69.2 / AISDLC-98). The
slash command body runs in the main Claude Code session which DOES have
Agent, so it can spawn ci-conflict-resolver directly. This is the
same architecture pattern as /ai-sdlc rebase and /ai-sdlc execute.
Hard rules (NEVER violate)
- Never merge a PR. Do not run
gh pr mergefor merge —gh pr merge --autois the re-arm path the agent owns and is explicitly permitted (it does NOT merge; it only re-attaches the auto-merge request that the force-push cleared per AISDLC-356). - Never force-push with plain
--force/-f. Always use--force-with-lease. The agent enforces this; this command does not push directly. - Never push to
mainormaster. The agent refuses; this command also refuses at Step 1. - Never close PRs or issues.
- Never delete branches.
- Never edit
.ai-sdlc/**or.github/workflows/**. - Never write GitHub Actions CI-skip magic tokens. (AISDLC-88.)
Step 0 — Validate input
PR=$ARGUMENTS
if [ -z "$PR" ] || ! echo "$PR" | grep -qE '^[0-9]+$'; then
echo "ERROR: pass a PR number, e.g. /ai-sdlc resolve-conflicts 1234"
exit 1
fi
Step 1 — Locate PR + worktree
gh pr view "$PR" --json number,title,headRefName,headRefOid,body,state,mergeStateStatus,statusCheckRollup \
> /tmp/resolve-conflicts-pr-${PR}.json
BRANCH=$(jq -r '.headRefName' /tmp/resolve-conflicts-pr-${PR}.json)
HEAD_SHA=$(jq -r '.headRefOid' /tmp/resolve-conflicts-pr-${PR}.json)
TITLE=$(jq -r '.title' /tmp/resolve-conflicts-pr-${PR}.json)
# Refuse on main/master (Hard Rule 3).
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
echo "ERROR: refusing to operate on protected branch $BRANCH"
exit 1
fi
TASK_ID_LOWER=$(echo "$BRANCH" | sed -E 's|^ai-sdlc/([a-z]+-[0-9.]+).*|\1|')
WORKTREE_PATH=".worktrees/$TASK_ID_LOWER"
if [ ! -d "$WORKTREE_PATH" ]; then
git fetch origin "$BRANCH"
mkdir -p .worktrees
git worktree add "$WORKTREE_PATH" "origin/$BRANCH"
fi
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.
- 4d ago First seen · 208 lines · 85 tokens per session scan A 94d9fd65135b
resolve-conflicts is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (100 stars, last pushed 10d ago), licensed Apache-2.0. It adds 85 tokens to every session and 2,158 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.
session-stop
Stop recording and save this agent session to the project ledger.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
ox-session-pause
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Suspend the current session recording. Local cache continues to receive entries, but the upload at stop time will exclude the suspended range.
au-aescsf
You are an enterprise architect generating an Australian Energy Sector Cyber Security Framework (AESCSF) maturity assessment for an Australian energy-sector project, asset, market interface, OT environment, DER platform, or regulated energy business capability.