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/desplega-ai/agent-swarmWrote 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/desplega-ai/agent-swarm/create-pr)<a href="https://agentmods.dev/commands/desplega-ai/agent-swarm/create-pr"><img src="https://agentmods.dev/badge/commands/desplega-ai/agent-swarm/create-pr/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/desplega-ai/agent-swarm/create-pr"><img src="https://agentmods.dev/badge/commands/desplega-ai/agent-swarm/create-pr.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.00019 | $0.01021 |
| Opus 5.5 | $0.00008 | $0.00408 |
| Sonnet 5.5 | $0.00004 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
create-pr 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 13d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request / Merge Request
Create a PR (GitHub) or MR (GitLab) from the current branch with an auto-generated title and description.
Provider detection: Check the remote URL:
- If
github.com→ useghCLI - If
gitlab.comorgitlab.→ useglabCLI
Arguments
base-branch(optional): Branch to merge into (defaults tomainor repo default)
Prerequisites
You should be working in a repository cloned to /workspace/personal/<repo-name>.
Workflow
- Verify state — confirm you're in a git repo, not on main/master, and have commits to push.
- Run PR checks (MANDATORY) — Run ALL checks listed in the "PR Checks" section of your Repository Guidelines. Run each command/task sequentially. If ANY check fails, fix the issue and re-run until all pass. If no guidelines are defined, check the project's CLAUDE.md for a pre-PR checklist and run those. Do NOT proceed until all checks pass.
- Push the branch —
git push -u origin HEAD - Gather context — review commit messages and changed files since diverging from base.
- Generate title and description. Follow the conventions of the repository you are working in, not a fixed format:
- Title: Concise summary (conventional commit style if the repo uses it)
- Description: If the repo has a PR/MR template, use its headings as the structure and fill every section. GitHub looks for
pull_request_template.mdin.github/,docs/, or the repo root (plus an optionalPULL_REQUEST_TEMPLATE/directory), and falls back to the org's.githubrepo. GitLab uses.gitlab/merge_request_templates/. Also follow any PR rules in the repo'sCLAUDE.md,AGENTS.md, orCONTRIBUTING.md. If the repo defines none, include: summary of changes, notable items, testing done, related issues. - Show the change, do not narrate it. Aim for about 250 prose words; code blocks, mermaid, tables and
<details>do not count. No file-by-file changelog: that belongs in your task output. - Review map: build it from
git diff --stat <base>...HEAD. One row per area, biggest risk first, with(+N/-M), a depth (🔍 deep, 👀 skim, ⏭ skip for tests and generated files) and what could break. - Change outline: 1 or 2 views of the shape of the change. Pseudocode with
+/-lines for logic, mermaid for flow, a tree with paths on the nodes for structure. - Swarm provenance (when you run in the swarm): fill it from your task context. Link the task (
$APP_URL/tasks/<taskId>) and its tree ($APP_URL/sessions/<rootTaskId>), the Slack permalink of the ask if the task came from Slack, any workflow run, and the plan or research as anagent-fs share-createlink plus its durablelive.agent-fs.devpath. These auth-gated links go in this section only. - Media: images and mp4s as GitHub user attachments (
github-attachskill), docs asagent-fs share-createlinks. Never a presigned agent-fs URL for docs or videos.
- Create the PR/MR using
gh pr createorglab mr create.gh pr create --bodydoes not apply the repo template, so write the filled description to a file and pass it with--body-file <file>. - Check CI status — After creating the PR, wait ~30 seconds, then check CI with
gh pr checks <pr-number>(GitHub) orglab mr view --json pipelines(GitLab). If any check is failing, investigate the failure, fix it, push the fix, and re-check. Repeat until CI is green. - Report the PR/MR URL and CI status.
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.
- 13d ago Changed · +6 lines ea2470d201e6
- 26d ago Changed 6bd228870975
- 1mo ago First seen · 40 lines · 19 tokens per session scan A cd55ee31c8f3
create-pr is a command published in the GitHub repository desplega-ai/agent-swarm (910 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,021 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
tokenless-stats
Show Tokenless compression statistics.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.
rollback
An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
update
Check for and apply KARIMO updates from GitHub releases.
buzz-crawling
A command that starts an external public-opinion research and strategy-update workflow. The description does not specify which sources it uses or what output it produces.