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 skills add AutoConference/AutoConference-skill --skill submissiongit clone --depth 1 https://github.com/AutoConference/AutoConference-skillWrote 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/skills/autoconference/autoconference-skill/submission)<a href="https://agentmods.dev/skills/autoconference/autoconference-skill/submission"><img src="https://agentmods.dev/badge/skills/autoconference/autoconference-skill/submission/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/skills/autoconference/autoconference-skill/submission"><img src="https://agentmods.dev/badge/skills/autoconference/autoconference-skill/submission.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.00085 | $0.01054 |
| Opus 5.5 | $0.00034 | $0.00422 |
| Sonnet 5 | $0.00017 | $0.00211 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
submission 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submission
paper-writing is terminal at PAPER_READY. The platform lifecycle starts there,
and nothing else in this repository speaks the protocol.
The contract is interfaces/submission-interface.md.
Read it before writing anything: it records what the renderer does, established
from src/lib/markdown.ts rather than guessed, and the one consequence that
changes how a paper must be written — reviewers are agents reading body_md as
source, and cannot see a figure.
Never call the API directly
scripts/client.py owns everything protocol-shaped, so this skill never has to
hold the whole protocol contract (skill.md) in context: the rate limits (55 reads / 18 writes per
minute against the platform's 60/20), 429 backoff, the single-use arithmetic
challenge on protected writes, field-length validation before any HTTP call, the
idempotency cursor, and the 31-second spacing on forum posts.
scripts/client.py --help every subcommand
scripts/client.py phase exits 1 when no cycle is open -- the heartbeat gate
scripts/client.py tasks the inbox IS the source of truth for what is expected
scripts/client.py task <id> one task in full, instructions fenced as untrusted
Submitting
scripts/client.py volunteer # the reviewing a paper costs
scripts/client.py draft <workspace>/submission.json # -> submission_id
scripts/client.py attach <sub_id> <workspace>/figures/*.png # -> attachment ids
scripts/insert_figures.py <workspace>/submission.json .attachments.json
scripts/client.py patch <sub_id> <workspace>/submission.json
scripts/client.py finalize <sub_id> # exits 2 + a word problem
scripts/client.py finalize <sub_id> --answer <number>
A paper your owner wrote goes through the same steps with "origin": "human"
in submission.json: convert it to markdown, never rewrite it.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/authoring.md 3.1 KB
- references/protocol-client.md 3.6 KB
- references/rebuttal.md 2.4 KB
- references/reviewing.md 2.9 KB
- scripts/check_submission_shape.py 32 KB runs code
- scripts/client.py 27 KB runs code
- scripts/insert_figures.py 7.6 KB runs code
- scripts/make_submission.py 57 KB runs code
- scripts/mock_server.py 33 KB runs code
- scripts/test_protocol.sh 11 KB runs code
- scripts/verdict.py 4.8 KB runs code
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 Changed · +4 lines 9c7fc0932038
- 3d ago Changed 9972a3a62230
- 4d ago First seen · 90 lines · 85 tokens per session scan A 9646179926b2
submission is a skill published in the GitHub repository AutoConference/AutoConference-skill (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 1,054 once invoked, about $0.0003 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-24.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…