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/superplanehq/superplane/sync-maingit clone --depth 1 https://github.com/superplanehq/superplaneWhat 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.00021 | $0.00479 |
| Opus 5 | $0.00010 | $0.00239 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
sync-main 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 2d 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
Sync working branch with main
Update the current branch with the latest main branch changes from origin, merge main into the current branch, reconcile differences, and resolve merge conflicts.
Inputs
- Optional: remote name (default
origin) - Optional: base branch name (default
main)
Process
- Validate repo state:
- Confirm this is a git repository.
- Detect current branch (
git branch --show-current). - If current branch is
main, stop and ask for a feature branch.
- Check for local uncommitted changes:
- If dirty, auto-stash with a descriptive message before merge.
- Pull latest base branch state:
- Run
git fetch <remote> <base-branch>. - Inspect incoming changes from
<remote>/<base-branch>compared to current branch (git log --oneline --left-right --cherry-pick HEAD...<remote>/<base-branch>).
- Run
- Merge base into current branch:
- Run
git merge <remote>/<base-branch>. - If there are no conflicts, continue.
- Run
- If conflicts exist, resolve them fully:
- List conflicted files with
git status --short. - For each conflict, inspect both sides and reconcile intentionally (do not blanket-use
--oursor--theirs). - Preserve current branch intent while incorporating important fixes/changes from
<base-branch>. - Stage resolved files with
git add. - Complete the merge commit.
- List conflicted files with
- Validate the result:
- Run relevant tests/checks for changed areas.
- Ensure working tree is clean and merge is complete.
- If a stash was created:
- Re-apply it and resolve any follow-up conflicts.
- Re-run relevant checks if needed.
- Output summary:
- Current branch name.
- Latest fetched base branch commit.
- Whether conflicts were found and how many files were reconciled.
- Final merge commit SHA.
Constraints
- Do not force-push.
- Do not rewrite history unless explicitly requested.
- Prefer a standard merge commit (not rebase) for this command.
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.
- 2d ago First seen · 51 lines · 21 tokens per session scan A fcda134257d4
sync-main is a command published in the GitHub repository superplanehq/superplane (5,700 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 479 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
fix-pr-review-comments
Analyze PR comments, implement fixes, and post targeted responses.
OPSX: Sync
Sync delta specs from a change to main specs.
triage
Triage Linear issue with comprehensive analysis.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.