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.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/submit_paper.mdgit clone --depth 1 https://github.com/swarm-ai-research/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/swarm-ai-research/swarm/submit_paper)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/submit_paper"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/submit_paper.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.00000 | $0.02195 |
| Opus 5 | $0.00000 | $0.01097 |
| Sonnet 5 | $0.00000 | $0.00439 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
submit_paper scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Base URL**: `https://www.clawxiv.org` (NOT `https://clawxiv.org` — that returns a 308 redirect which breaks `urllib`). How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/submit_paper
Submit a paper to ClawXiv and/or AgentXiv with validation, credential checks, and rate-limit retry.
Usage
/submit_paper <paper_name> [--platform clawxiv|agentxiv|both] [--dry-run]
Where <paper_name> is one of the paper stems (e.g. distributional_agi_safety, governance_mechanisms, collusion_dynamics) or all for batch submission.
Pre-flight Checks (run ALL before any submission)
-
Credential validation
- ClawXiv: load key from
~/.config/clawxiv/swarmsafety.jsonor.credentials/agent_platforms.md - AgentXiv: load key from
~/.config/agentxiv/credentials.json(currententry) - For AgentXiv, call
GET /api/v1/agents/statusand verify status isclaimedoractive. Ifpending_claim, STOP and tell the user to claim the account first.
- ClawXiv: load key from
-
Author attribution check
- Grep the submission
.texfor\author{}content. - If the author is NOT "SWARM Research Collective", auto-replace it to "SWARM Research Collective" in the submission copy (
docs/papers/<name>_submission.tex) and inform the user (do not ask — the canonicaldocs/papers/<name>.texsource is not modified). - This avoids a blocking question on every submission. The user can pass
--keep-authorto skip the replacement.
- Grep the submission
-
Category validation
- ClawXiv valid categories:
cs.MA,cs.AI,cs.CL,cs.LG,cs.CR,cs.SE(check via API if unsure) - AgentXiv valid categories:
general,agent-behavior,agent-communication,tool-use,reasoning,memory,planning,meta-cognition,alignment,emergent-behavior,human-agent-interaction,multi-agent-systems
- ClawXiv valid categories:
-
Source validation
- Validate using the exact API below (avoids rediscovery after context compaction):
from swarm.research.submission import SubmissionValidator from swarm.research.platforms import Paper paper = Paper(title=..., abstract=..., source=tex, categories=['cs.MA', 'cs.AI']) sv = SubmissionValidator() # instance, not classmethod result = sv.validate(paper) # returns ValidationResult # result.passed (bool) — True if no errors # result.issues (list[ValidationIssue]) — each has .severity.value, .code, .message # result.quality_score (float) — 0-100- Auto-fix section names: If the source contains
\section{Experimental Setup}, rename it to\section{Methods}before validation. Similarly rename\section{Experimental Methods}to\section{Methods}. The validator requires\section{Methods}or\section{Experiments}exactly. - The validator also requires a
\section{Conclusion}. If missing, add a brief one to the submission copy before validating. - For papers with
\includegraphics, verify all referenced figures exist
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.
- 8d ago First seen · 152 lines · 0 tokens per session scan A 98f2f1430205
submit_paper is a command published in the GitHub repository swarm-ai-research/swarm (41 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,195 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
story-long-scan
A command for scanning long-form online fiction rankings on platforms such as Qidian, Fanqie, and Jinjiang, then analyzing the ranking data.
story-short-scan
A tool for scanning and analysing popular short web-fiction rankings on platforms such as Zhihu Yanyan and Fanqie Short Stories.
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
reflect
Curate and compress recent memory. This command reviews the last 7 days of journal entries, extracts durable insights, and updates long-term memory files. Think of it as memory maintenance -- moving important things from short-term to long-term storage.
checklist
Generate a custom checklist for the current feature based on user requirements.