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/marcusquinn/aidevopsWrote 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/marcusquinn/aidevops/sync-branch)<a href="https://agentmods.dev/commands/marcusquinn/aidevops/sync-branch"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/sync-branch/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/marcusquinn/aidevops/sync-branch"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/sync-branch.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.00007 | $0.00114 |
| Opus 5.5 | $0.00003 | $0.00046 |
| Sonnet 5.5 | $0.00001 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
sync-branch 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 1mo 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
Use the session-rename_sync_branch tool to rename this session to match the current git branch name only when no issue/PR-prefixed title is already set.
If working on an issue or PR, prefer an explicit title first and include the issue/PR title or a recognizable shortened form: Issue #123: Fix dispatch title prefix or PR #456: Refresh auth workflow tests.
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.
- 1mo ago First seen · 11 lines · 7 tokens per session scan A 3ceabdc02f6a
sync-branch is a command published in the GitHub repository marcusquinn/aidevops (423 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 114 once invoked, about $0.0000 per session on Opus 5.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-06.
Other commands, from other repositories
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
commit
Analyze uncommitted changes, create a branch if needed, and commit with a well-structured message.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
fact-check
Verify a generated document against actual code and git history.
release
Run the weekly release checklist (triage, CHANGELOG, semver tag, GitHub Release, dev.to, LinkedIn, ufawkes.dev) and file the post-release DORA issue.