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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/gh-resolve)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-resolve"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-resolve/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/synaptiai/synapti-marketplace/gh-resolve"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-resolve.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.00033 | $0.03835 |
| Opus 5 | $0.00016 | $0.01917 |
| Sonnet 5 | $0.00007 | $0.00767 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade B, and why
gh-resolve scanned grade B 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -z "$AUTO_RESOLVE" ] && AUTO_RESOLVE=$(jq -r '.conflictResolution.autoResolveTrivial // empty' "$HOME/.claude/settings.gh-workflow.json" 2>/dev/null) How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Merge Conflicts $ARGUMENTS
Detect, classify, and resolve merge conflicts with per-file strategy selection and full verification.
Tool Usage: This workflow uses the AskUserQuestion tool for conflict resolution decisions (delete-modify, competing changes, strategy overrides), TaskCreate/TaskUpdate tools to track per-file resolution progress, and the Skill tool for capability discovery.
Contract
GOAL: All merge conflicts resolved with no orphaned markers, quality checks passing, and merge/rebase completed. Testable: grep -rn '^<<<<<<<\|^=======\|^>>>>>>>' . 2>/dev/null | grep -v '.git/' | grep -v 'node_modules/' returns zero results AND git status --porcelain | grep '^[UAD][UAD]' returns zero results.
CONSTRAINTS:
- Never silently drop changes from either side of a conflict
- Always analyze both sides before choosing a resolution strategy
- Never auto-resolve delete-modify conflicts — require user decision
- Run quality checks after resolution to verify nothing broke
FORMAT: Conflict analysis table shown first, then per-file resolution with task tracking, then verification summary.
FAILURE CONDITIONS (output is unacceptable if any apply):
- Changes from either side silently dropped without rationale
- Orphaned conflict markers remain in any file
- Delete-modify conflict resolved without user decision via AskUserQuestion
- Quality checks not run after resolution
- Merge/rebase not completed after resolving all files
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.
- today First seen · 440 lines · 33 tokens per session scan B 57661f657e48
gh-resolve is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 3,835 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.
deploy
Start Phase 6 — propose a deployment for human approval and, once approved, execute with post-deploy verification.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.