swarm: Command for Claude Code

.claude/commands/submit_to_list.md

submit_to_list is a command for Claude Code from swarm-ai-research/swarm. It costs 0 tokens per session (855 once invoked), scanned A, original, MIT.

A command that submits a project to a curated GitHub list, such as an “awesome” repository. It uses GitHub’s command-line tool to create a fork, add the entry, and open a pull request for review.

In plain words
What is it for?
Use it to add a repository or paper to a curated GitHub list. It can help choose a section, draft an entry from the project details, and open the contribution for maintainers.
Why use it?
It removes the repetitive work of finding the right README section, matching its entry style, and preparing the contribution. It also checks that GitHub command-line access is available.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is swarm-ai-research/swarm's own configuration. It tells Claude Code how to work on swarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything swarm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/submit_to_list.md
Clone the repo
git clone --depth 1 https://github.com/swarm-ai-research/swarm

Made for: Claude Code.

Wrote 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.

agentmods badge for submit_to_list

README.md
[![agentmods](https://agentmods.dev/badge/commands/swarm-ai-research/swarm/submit_to_list/github.svg)](https://agentmods.dev/commands/swarm-ai-research/swarm/submit_to_list)
Your own site
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/submit_to_list"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/submit_to_list/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.

agentmods 80×15 button for submit_to_list

Your own site · 80×15
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/submit_to_list"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/submit_to_list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 855 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00855
Opus 5 $0.00000 $0.00428
Sonnet 5 $0.00000 $0.00171
Haiku 4.5 $0.00000 $0.00085

Measured 9d ago against content hash d8bcc5ff7084, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

submit_to_list 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 9d 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.

.claude/commands/submit_to_list.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/submit_to_list

Fork an external GitHub repo, add an entry to a curated list (e.g. awesome-*), and open a PR — all via gh CLI.

Usage

/submit_to_list <owner/repo> <section-name> [entry-text]

Examples:

  • /submit_to_list kyegomez/awesome-multi-agent-papers "Social Simulation & Agent Societies"
  • /submit_to_list Giskard-AI/awesome-ai-safety "General ML Testing" '* [My Paper](https://example.com) (Author, 2026) \#Safety`'`

Behavior

1. Validate inputs

  • Parse <owner/repo> into owner and repo.
  • Confirm gh auth status works. Abort if not authenticated.
  • If <section-name> is not provided, fetch the README and list available sections for the user to choose from.

2. Fetch and understand the target list format

  • Fetch README.md from the upstream repo via gh api repos/<owner>/<repo>/contents/README.md.
  • Find the target section by heading match.
  • Detect the entry format from existing entries in that section (e.g. - **[Title](URL)** vs * [Title](URL) (Author, Year) \#Tag``).
  • If [entry-text] is not provided, draft an entry using the detected format and the project info from this repo (paper title, repo URL, author, tags). Present the draft to the user for confirmation before proceeding.

3. Fork the repo

gh repo fork <owner>/<repo> --clone=false
  • If the fork already exists, skip this step.
  • Detect the fork owner from gh auth (usually the authenticated username).

4. Create a branch

  • Get the default branch SHA: gh api repos/<fork-owner>/<repo>/git/refs/heads/<default-branch>
  • Create branch add-distributional-agi-safety: gh api repos/<fork-owner>/<repo>/git/refs -X POST

5. Insert the entry

  • Fetch the README from the fork.
  • Find the last entry in the target section (before the next ## heading or end of file).
  • Insert the new entry after the last existing entry in the section.
  • Push the updated README to the branch via gh api repos/<fork-owner>/<repo>/contents/README.md -X PUT.

6. Open the PR

Read the full file on GitHub · 90 lines

Changes

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.

  1. 9d ago First seen · 90 lines · 0 tokens per session scan A d8bcc5ff7084

Subscribe to this mod's changes

submit_to_list is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 855 tokens. 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.