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/resolve)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/resolve"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/resolve.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.1 | $0.00038 | $0.02475 |
| Opus 5 | $0.00019 | $0.01238 |
| Sonnet 5 | $0.00008 | $0.00495 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
resolve 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 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.
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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Merge Conflicts
4-phase EXPLORE > PLAN > CODE > VERIFY workflow for merge conflict resolution.
Required Skills
merge-conflict-resolution— conflict detection, classification, and resolution strategiescapability-discovery— discover build/test/lint commandsdebugging-patterns— on-demand if resolution breaks the build
References
references/escalation-format.md— canonical six-field structure used by the max-conflict-files escalation (Phase 1) and any semantic/structural/delete-modify escalation surfaced during resolution
Phase 0: Pre-Flight
Determine invocation mode from $ARGUMENTS:
- No args + active conflict markers → resolve in-progress merge/rebase
- PR number → fetch PR, attempt merge against base, resolve conflicts
- Branch name → resolve conflicts for that branch against default branch
Validation
# Take the first whitespace-separated token; accept only if it matches the
# safe set [a-zA-Z0-9._/-] (covers digit-only PR numbers AND typical branch
# names like `feature/foo-bar.v2`). A token containing shell metacharacters
# (`;`, `|`, `$`, spaces, etc.) is rejected with empty RESOLVE_TARGET so the
# trailing context can't reach downstream shell. Trailing prose after the
# first whitespace is fine.
#
# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`.
_RAW="$ARGUMENTS" # Claude Code substitutes the bare arg token, not bash parameter-expansion
ARG1="${_RAW%% *}"
case "$ARG1" in
''|*[!a-zA-Z0-9._/-]*) RESOLVE_TARGET="" ;;
*) RESOLVE_TARGET="$ARG1" ;;
esac
echo "### Resolve Mode"
# Quote parenthesized fallback per command-output-format.md rule 2.
echo "RESOLVE_TARGET=${RESOLVE_TARGET:-\"(none — in-progress merge mode)\"}"
if [ -f .git/MERGE_HEAD ] || [ -d .git/rebase-merge ] || [ -d .git/rebase-apply ]; then
echo "CONFLICT_STATE=active"
else
echo "CONFLICT_STATE=inactive"
fi
true
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 · 272 lines · 0 tokens per session scan A 7bf22c8c0df1
resolve is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,475 once invoked, about $0.0002 per session on Opus 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 commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
fix
Quick bugfix commit. Use for fix bug, bugfix, patch, hotfix, correct error.
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
bug-hunter.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects Ornek cikti.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
resolve-conflicts
Guide semantic resolution of an in-progress merge or rebase conflict, side by side.